Looking for feedback on simplifying self hosting
Looking for feedback on simplifying self hosting
Hi all,
I started self hosting nextcloud only. Now I have a domain name and I would like to selfhost more services and websites on subdomains without having to open up more ports on my router.
- Is it reasonable to use a reverse proxy server to avoid opening up more ports?
- Can I use a reverse proxy manager that simplifies SSL certs, etc?
- Can I put the HTTP/HTTPS services behind a reverse proxy, behind a free cloudflare DNS proxy to mask my IP address?
- And put other non-http services on the real IP address.
- Will all of this be more prone to failure and slow compared to forwarding 443 and 80 directly to my nextcloud server?
The other services I would like to eventually host and have accessible externally are
- Jitsi
- Mastodon instance (hoping to make some bots that mirror other social media to bring them into Mastodon)
- blog website
- Veilid maybe
- OpenVPN over TCP on 443 (to get through restrictive firewalls on e.g. school wifi networks that don't whitelist domains)
- Synology to Synology backup.
I'm hoping to use Yunohost on a RPI to simplify hosting a lot of these things.
Here's my plan where I'm looking for feedback. Am I missing any steps? Are my assumptions correct?
- Install reverse proxy on yunohost; configure cloudflare DNS and freedns.afraid.org to point towards the reverse DNS server.
- Configure the reverse DNS to redirect various subdomains to
- the raspberry pi running nextcloud
- the other raspberry pi running openvpn
- the Synology running the backup service
- services running on the yunohost raspberry pi
I have not been able to find good documentation about how to configure the yunohost reverse proxy, or how to deal with HTTP headers, or have correct certificates on all the subdomains as well as the reverse proxy. Looking for advice on how to move forward and or simply this setup.
Yes this is possible. I have a few hosted items with subdomains and I have it set up as follows:
All subdomains point to the same IP. Router port forwards all 80/8080 traffic to server. I use Caddy in Docker to forward the requests based on the subdomain to the appropriate docker container hosting the actual service.
This makes spinning up something new simple. You get a docker container of New Thing going, edit the CaddyFile to point to it too, set up new subdomain in cloudflare. No new open ports needed.
Hope this helps!
Thanks, this is definitely the way I would like to go!
- Can Caddy forward requests to other machines on the LAN?
- Have you ever had to mess with HTTP headers?
- Do the docker containers have to get certificates from let's encrypt, or is caddy the only part that needs to manage a wildcard certificate?
- I think it can, you just need to give it the machine's name or local IP and the port.
- Nope!
- Caddy handles all certs from LE and renews them for you too. Nothing you need to do on your own.
I'd look at wireguard / tailscale / headscale and hide your services behind a vpn
If you decide to not got the YunoHost route, I like the way this guide did reverse proxies with Caddy: https://github.com/DoTheEvo/selfhosted-apps-docker.
Caddy is the answer. Makes running a reverse proxy with certs totally straight forward.
Thank you, this looks like a great guide
Check out yunohost.org (and similar projects) If you're in for a turnkey-solution.
But yes, a reverse proxy that does all the work and handles SSL is a nice solution. I also use that. It's relatively easy to set up, doesn't really slow down anything and makes a lot of stuff easier to manage.
I use NGinx, but Caddy or Traefik will do the same. And I don't use Cloudflare, so I can't comment on that.
And btw, Jitsi-Meet is going to require some more dedidated ports for the WebRTC, STUN, etc
Im just new with yunohost.org but it does seem to make installing applications very simple. Users, email, reverse proxy.
Yeah, what @anamethatisnt@lemmy.world suggested is definitely the easiest thing and super practical - I got family members on my tailnet for this purpose. I am however now also looking into some kind of tunneled, reverse proxied and authenticated way to expose a few of my services to other friends where I don't want to have to put them on tailscale or potentially expose them to more than needed via that route.
I haven't started yet, but I am updating my network set up soon to install a dedicated OPNsense router as the edge for my network. From there, the plan is to have a cloudflare tunnel that accesses some of these services via a caddy reverse proxy, with Authelia for authentication. That's the part I have studied enough to feel confident I can do. I am a little weaker on the networking aspects of this, which is where I need to study some more - like isolating those services that are exposed in my network, while still giving them access to some other needed resources within it, etc.
Tailscale has the Funnel feature, which can funnel traffic into your Tailscale net for you.
Ooooh that looks interesting. I haven't messed around much with tailscale since I set it up a few years back and hadn't noticed this. Funny, I was just the other day wondering if they might have something like that, but didn't look it up. Thanks!
You can also run a free cloudflare tunnel. It's what I us3 so I don't have to open a port for my nextcloud but still want it to be able to sync to my phone while not on vpn
Interesting, I already use cloudflare DNS and had "proxy" turned on for nextcloud, but I still had to open 80 and 443 on my router, so I'll look up how to set up the free tunnel sometime
I would avoid exposing services to the internet especially in a home network. I would look into Tailscale.
In a perfect world I would do this, but for nextcloud at least, I have to be able to access it from public computers where I cannot install and configure tailscale.
Sometimes I want to share services with friends and family too.
And Synology support for tailscale sounds like it's finicky unfortunately.
Don't access Nextcloud from public computers as that is very bad for security.
If you must expose it to the internet I would strongly recommend all of the hardening stuff and isolating the deployment to its own vlan with limited access. Remember to follow least privilege and defense in depth. You can find more information on these two concepts online. Account for two pieces of software having serious security issues. (Thus have multiple layers an attacker needs to bypass plus monitoring)
You seem pretty focused on reverse proxies for some reason, but that isn't security. An alternative is a VPN into your network. Simple solution that solves all of your asks if you don't need many people accessing your services.
I would like to use tailscale for some services, but the ones I access from public computers, like nextcloud or blog hosting, can't be behind a VPN.
I would love the Synology to Synology backup to be behind the VPN, but I'm not sure I'll be able to get it working, so that is lower down on my list.
Things like Jitsi would be cool to have behind the vpn, but then I'd have to get everyone to install tailscale on their phones and configure access, so that's going to be too complicated for me and my family unfortunately.
There’s a good document from the SWAG reverse proxy that explains it all. I reverse proxy everything on my unraid server through swag and have for years.
Lots of options. Here's what I do:
- HAProxy - uses SNI to match an HTTPS request to a service, without decrypting the connection
- Caddy - manages TLS certificates, decrypts connections, and sends the request to the relevant service
- Docker - each service runs in a docker container on the host
- my router has static DNS entries for each of my subdomains, so I can do https://service.mydomain.com, and my traffic never leaves my LAN when I'm at home
I have HAProxy running on my VPS (Hetzner), and it routes traffic over my WireGuard VPN to whatever physical device on my internal network handles that service (i.e. 2). This allows me to add devices to my network as needed, and TLS certs all live on that device.
This is probably overkill for your setup since it sounds like you can talk to your home router from the internet (I can't because I'm behind CGNAT), so you could drop #1 and just use Caddy, assuming you're okay with having all traffic handled by a single device. Or you can see if your router supports SNI-based routing to handle what I'm using HAProxy for.
If you don't need to share your services w/ anyone, you can have everything live inside of a VPN and just access it via that VPN. You can look into Tailscale if you want something dead simple, and I think Cloudflare offers something similar. I started with that, but decided I wanted to share a number of services with family members, and I didn't want to force each of them to configure my VPN.
Thanks for the information. I will have to look into SNI and see if my router can support it -- if I move someday to an ISP behind a more restrictive firewall, this system looks pretty good. (Or if I get unhappy with one reverse proxy handling everything).
Thank you everyone for the suggestions, I learned a lot and I'll continue to check back also.