I never open any ports to the open Internet other than the two my friend client uses.
For remote access I use a P2P VPN called ZeroTier leaving it always running on the Pi, and switching it on for the remote device when needed. It’s free for up to like 50 users and is very powerful, but dead simple.
Never open ports to the internet unless you want everybody to see it. Always use VPN to access your selfhosted stuff. If you’ve got a lot of VPN connections to set up, try generating a QR code for the connection. Makes it a bit faster to setup the client.
May I ask what do you guys have exposed to the internet?
I personally just have a wireguard VPN (single UDP port open) and everything is accessible through an internal reverse proxy. I just never felt the need to expose nothing ant least not web related.
I have Jellyfin and Jellyseerr open through cloudflare -> nginx over port 443 so i can share it with friends. Eventually I’ll do the same with NextCloud probably.
Hmm I thought if I set it up to not cache data it would be fine, but it turns out that was outdated data. I don’t see an option for paying for it unless I host media specifically on their servers which I won’t be doing.
I doubt I’ll be using a significant amount of data but if they give me a warning I’ll have to turn off the tunnel I suppose. Thanks for the question!
I expose self-hosted bitwarden for my family to access through cloudflared tunnels and only allowing US IP via cloudlfare rules. Only the webUI is exposed and traffic has to go through cloudflare and nginx to be able to do anything.
That’s exactly how I have my setup, and on my client WireGuard configs I have it set to split route so I can connect to my home VPN without disrupting anything else.
One thing I need to publicly expose is my own instance of Mealie. It’s a recipe manager that supports multiple users. I share it with family and friends, but also with more distant acquaintances. I don’t want to have to provide and manage access to my network for each and every one of them.
I’ve never heard of NextCloud Cookbook before. Looking at its Github page, it says it’s “mostly for testers” and is unstable, so no point in even considering it for regular use at this point in time. Besides, I’m assuming you’d need to have your own instance of Nextcloud up and running to use it; I don’t use Nextcloud.
As for Grocy and other more mature alternatives (Tandoori also comes to mind), I think I initially went with Mealie because it had the most pleasant UI out of all of them. I liked it and found that it satisfied all of my requirements, so I just kept using it.
Do you even need a reverse proxy if you’re using Tailscale? What advantage does it give you over setting up your DHCP correctly such that you can access your services by hostname?
Because I have my own custom domain internally and don’t use tailscale while on I’m on my network physically. But I get the best of both worlds, however I do have Tailscale setup with DNsMasq to set to my domain name anyway instead of using the Tailscale domain
I’ve got a reverse proxy for stuff I want to be able to hit from the outside. It’s behind an SSO portal with 2fa (hardware token). Then for everything else I VPN in.
A reverse proxy isn’t a substitute for a VPN for access outside your network. And it isn’t any less secure; you only need to open 1 port however all of your services will be accessible via that single port which is arguably less secure.
Probably the usual. 80/443, wireguard, a couple game servers.
For those of you who staunchly put your open ports on a VPS and wireguard tunnel it back to your home server, are you firewalling that wg connection to only allow specific traffic?
I use a self-hosted vpn, because I don’t want to expose anything to the internet. The ones I do want to, I haven’t set up yet since it would require reinstalling my pi. But I do have a reverse proxy set up on a vps that I will use once I get around to doing it.
Currently I expose port 22 for SSH, 443 for Nginx and a couple extra for Syncthing (to mirror my media files between a Hetzner Storage Box and my NAS at home).
There’s a specific setup I tried to build once but didn’t manage:
Expose only Wireguard port from my VPS
make it so that when (and only when) a device is connected to the VPS via Wireguard, then mydomain.xyz will target the VPS’ IP (and therefore hit my Nginx proxy which redirects to my various services at myservices.mydomain.xyz.
I tried by having a Adguard Home running on that same VPS, and setting its IP as the DNS in the wg0.conf that goes on the client device but it didn’t work.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
I never open any ports to the open Internet other than the two my friend client uses.
For remote access I use a P2P VPN called ZeroTier leaving it always running on the Pi, and switching it on for the remote device when needed. It’s free for up to like 50 users and is very powerful, but dead simple.
free for 25 users
Never open ports to the internet unless you want everybody to see it. Always use VPN to access your selfhosted stuff. If you’ve got a lot of VPN connections to set up, try generating a QR code for the connection. Makes it a bit faster to setup the client.
May I ask what do you guys have exposed to the internet?
I personally just have a wireguard VPN (single UDP port open) and everything is accessible through an internal reverse proxy. I just never felt the need to expose nothing ant least not web related.
I have Jellyfin and Jellyseerr open through cloudflare -> nginx over port 443 so i can share it with friends. Eventually I’ll do the same with NextCloud probably.
Video streaming is against Cloudflare policies, aren’t you worried that they’ll may block your account?
Hmm I thought if I set it up to not cache data it would be fine, but it turns out that was outdated data. I don’t see an option for paying for it unless I host media specifically on their servers which I won’t be doing.
I doubt I’ll be using a significant amount of data but if they give me a warning I’ll have to turn off the tunnel I suppose. Thanks for the question!
I expose self-hosted bitwarden for my family to access through cloudflared tunnels and only allowing US IP via cloudlfare rules. Only the webUI is exposed and traffic has to go through cloudflare and nginx to be able to do anything.
a lot of stuff:
than i have stuff only accessible from local, like the *arr stack.
i’m not using cloudflare or anything, should I?
the only exposed ports i have are http / https and a random port for ssh.
i also don’t use any sso… maybe i should set one up.
KitchenOwl, and a Matrix server and Element web interface.
Just Navidrome for music streaming.
That’s exactly how I have my setup, and on my client WireGuard configs I have it set to split route so I can connect to my home VPN without disrupting anything else.
One thing I need to publicly expose is my own instance of Mealie. It’s a recipe manager that supports multiple users. I share it with family and friends, but also with more distant acquaintances. I don’t want to have to provide and manage access to my network for each and every one of them.
What made you pick Mealie over other stuff like Nextcloud Cookbook or Grocy or whatnot?
I’ve never heard of NextCloud Cookbook before. Looking at its Github page, it says it’s “mostly for testers” and is unstable, so no point in even considering it for regular use at this point in time. Besides, I’m assuming you’d need to have your own instance of Nextcloud up and running to use it; I don’t use Nextcloud.
As for Grocy and other more mature alternatives (Tandoori also comes to mind), I think I initially went with Mealie because it had the most pleasant UI out of all of them. I liked it and found that it satisfied all of my requirements, so I just kept using it.
Tailscale with reverse proxy, nothing publicly exposed
Do you even need a reverse proxy if you’re using Tailscale? What advantage does it give you over setting up your DHCP correctly such that you can access your services by hostname?
Because I have my own custom domain internally and don’t use tailscale while on I’m on my network physically. But I get the best of both worlds, however I do have Tailscale setup with DNsMasq to set to my domain name anyway instead of using the Tailscale domain
deleted by creator
I have two nginx ingress running on my cluster. One of private one public. Public one is what’s exposed on 80 and 443 to the net.
The private is only available via VPN or lan. The public is for services I want internet exposed.
My family have a VPN network set up to my lan on their router and have access to most services but the public stuff is for the internet friends
Depending on the services you provide, the usual standard ports. So if you run http/https services, port 80 and 443 respectively.
You seem to answer your own question.
I’ve got a reverse proxy for stuff I want to be able to hit from the outside. It’s behind an SSO portal with 2fa (hardware token). Then for everything else I VPN in.
What are you using for SSO?
Not op, but I’d recommend looking in to keycloak.
I’m not OP but Keycloak is pretty usable for SSO. I’ve configured about 8 different web apps to be integrated with it via OAuth2.
VPN because I don’t know enough about all the random arrr services to expose them trustworthily.
Reverse proxy and allowing connection only to IPs from my country.
A reverse proxy isn’t a substitute for a VPN for access outside your network. And it isn’t any less secure; you only need to open 1 port however all of your services will be accessible via that single port which is arguably less secure.
Everything that is managed by that RP, yes. One should obviously be careful when selecting what to expose.
deleted by creator
Probably the usual. 80/443, wireguard, a couple game servers.
For those of you who staunchly put your open ports on a VPS and wireguard tunnel it back to your home server, are you firewalling that wg connection to only allow specific traffic?
I used to, but less so now, I get that weakens the separation.
Mostly the vps is hardened to f and that’s my defense but I agree it’s a bad one.
I use a self-hosted vpn, because I don’t want to expose anything to the internet. The ones I do want to, I haven’t set up yet since it would require reinstalling my pi. But I do have a reverse proxy set up on a vps that I will use once I get around to doing it.
Currently I expose port 22 for SSH, 443 for Nginx and a couple extra for Syncthing (to mirror my media files between a Hetzner Storage Box and my NAS at home).
There’s a specific setup I tried to build once but didn’t manage:
mydomain.xyzwill target the VPS’ IP (and therefore hit my Nginx proxy which redirects to my various services atmyservices.mydomain.xyz.I tried by having a Adguard Home running on that same VPS, and setting its IP as the
DNSin the wg0.conf that goes on the client device but it didn’t work.