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.
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
I've hidden everything behind Wireguard.
externally my server doesn't even have open ports. everyone who uses my services gets a Wireguard key.
don't know how many people you wanna service or if it's just you - then Wireguard could be a viable solution
Same here, I'm too paranoid and checking access logs and attempts made me to stop keeping any other port open than wireguard.
How do you handle services that run on devices that can't implement wireguard, like say a Roku or something? Just don't allow?
in my case Wireguard acts as access to my personal LAN, where all my services (in virtual containers or physical computers) are located. I'm just pointing to their address inside my LAN, which I can access through Wireguard.
Google cloudflared tunnels, zeroteir and tailscale. They all solve this exact problem, I've been using cloudflared tunnels to host without exposing my ip for while now, it's relatively easy for https services.
Edit: also just because services require login, doesn't necessarily make them secure if their implementation is terrible. It's best practise to use a reverse proxy like nginx which specialises in having not shit security for authentication, and proxy your services behind it.
If you are cool with using Cloudflare, you can use Argo Tunnel to expose HTTP(S) services to the internet with DDOS protection and all of Cloudflares features.
They've made it free some time ago, you just need a pc/server in your network running the cloudflare agent software.
You have several options these days:
Use cloudflare in DNS proxy mode and run a dynamic DNS updater so cloudflare always point to your correct IP address. By using cloudflare DNS in proxy mode, your real IP address will be hidden because all traffics will be routed via cloudflare servers first. The disadvantage is it only works for http/https service. If you need to route other service/port (e.g. ssh) you'll need to use cloudflare tunnel
Rent a small vps and use it as a bastion server. Add your home server and the vps server into tailscale or zerotier network, and then configure it to route traffics to your home server. I personally use this method because it gives me full control and flexibility over using cloudflare, but it does harder to setup.
I've had to find a solution similar to what you are looking for. My need was due to being double NAT'ed where I had no control over the internet facing router/NAT.
Personally, my solution was to use Oracle Clouds free tier service to host and NGINX reverse proxy as Oracle also offers free static IPs to there compute instances. From there I used Tailscale to join the instance to a Proxmox container running Docker on my server running services I wanted exposed to the internet (Emby, and a few 'Arrr apps). I've found it to be remarkably stable (much more than I expected).
An alternative method is to use Cloudflare tunnels, which are very easy to get setup. It in essence is the same principle as above but using Cloudflare's 'reverse proxy as a service' type product. I was not able to use this for my needs as Cloudflare do not allow media streaming.
If you do choose the first option, I would recommend isolating the server running the exposed services to its own network that cannot touch your day-to-day network. I also recommend configuring ACLs in Tailscale to restrict traffic to specific ports from specific hosts to minimise any risk of having exposed services. Oh, and automatic updates to the OS and services is ideal.
I saw you are using basic HTTP auth, whilst it is secure enough it does have some issues with making connections more difficult, particularly if you are using any of your services API's (it is also not the best user experience IMO). I would recommend setting up oAuth/SSO if yunohost supports it.
Lastly, as other users have said, even if you don't use either suggestion, put a reverse proxy on it. NGINX Proxy Manager is a nice friendly solution with a web GUI if you are not too familiar with proxy configs
You have several options these days:
Use cloudflare in DNS proxy mode and run a dynamic DNS updater so cloudflare always point to your correct IP address. By using cloudflare DNS in proxy mode, your real IP address will be hidden because all traffics will be routed via cloudflare servers first. The disadvantage is it only works for http/https service. If you need to route other service/port (e.g. ssh) you'll need to use cloudflare tunnel
Rent a small vps and use it as a bastion server. Add your home server and the vps server into tailscale or zerotier network, and then configure it to route traffics to your home server. I personally use this method because it gives me full control and flexibility over using cloudflare, but it does harder to setup.
Running a federated service on your home network is just a bad idea in general. You're screaming to the world "hey look, there's a server running potentially exploitable software here!" Even if you hide the IP behind a VPN.
For everything else not so public as a federated service, best bet is to install a WireGuard VPN server on your network. Set it to some random high number port. Undetectable, basically. Then when you're away from home just connect to the VPN and it's basically just like you're still hooked to your WiFi at home.
If you are the only one using your services, sure but that's way more of a PITA than 99% of users are going to put up with. Running a federated service is no different than running any other service - harden your network, use tunneling if you so desire (though if hosting media, the likes of Cloudflare are out of the question), have your local VLANs configured accordingly, and manage it like you would any other service. Hell, if you are super paranoid, go dual WAN as that's likely cheaper than having a multiple VPS for your services or paying for the needed bandwidth on one (again, assuming media hosting)