Selfhosted

40113 readers

786 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Help me get started with VPN (lemmy.world)

submitted 9 months ago* (last edited 9 months ago) by PlutoniumAcid@lemmy.world to c/selfhosted@lemmy.world

33 comments fedilink hide all child comments

TLDR: VPN-newbie wants to learn how to set up and use VPN.

What I have:

Currently, many of my selfhosted services are publicly available via my domain name. I am aware that it is safer to keep things closed, and use VPN to access -- but I don't know how that works.

domain name mapped via Cloudflare > static WAN IP > ISP modem > Ubiquity USG3 gateway > Linux server and Raspberry Pi.
80,443 fowarded to Nginx Proxy Manager; everything else closed.
Linux server running Docker and several containers: NPM, Portainer, Paperless, Gitea, Mattermost, Immich, etc.
Raspberry Pi running Pi-hole as DNS server for LAN clients.
Synology NAS as network storage.

What I want:

access services from WAN via Android phone.
access services from WAN via laptop.
maybe still keep some things public?
noob-friendly solution: needs to be easy to "grok" and easy to maintain when services change.

you are viewing a single comment's thread
view the rest of the comments

[–] rambos@lemm.ee 3 points 9 months ago (1 children)

Not expert, but basically you should port forward wireguard port 51820 to your server, install wireguard server, create client(s) and load QR code (or config) on android/laptop and you are set. Pi hole DNS and everything else should work just like when you are on home wifi.

You can leave your CF for public access, but do you really need PF 80 and 443 if you are using CF tunnels? (I thought you dont, but I never used CF. Feels like its more safe to hve CF tunnels if you dont need to PF, but you have a middle man you have to trust)

[–] PlutoniumAcid@lemmy.world 2 points 9 months ago

Thank you for providing specific steps that I can take! I will look into this.

No I do not use cloudflare tunnels, just regular cloudflare to publish my services to the whole world - which is a concern of course.

Going with a connection from my device via wireguard sounds like just the right thing to do.