The comments give some great advice on what to self host, but my advice to you before you start spinning up a million services is to DOCUMENT EVERYTHING.
Seriously, document as you go and you will thank yourself later. Document niche commands you found online that worked, docker compose files, IP addresses/hostnames, where you put that random config file.
There are some great self hosted wiki and documentation products out there, start with that, then build the fun stuff!
Seconding Beszel, it’s dead simple to install, and add systems to. I love the sleek interface, and the ability to send notifications to a slew of services (like ntfy)
I’ve honestly never tried it, since I have the only node in my home network serve the local subnet. It allowed me to statically assign IPs at home and still use them outside of the house. I suppose there’s nothing stopping you from using the overlay network, especially if you have all devices involved on the Tailscale network, but I didn’t feel like doing that :)
Something that might help with using Tailscale and reverse proxying: you don’t have to use the IPs given to you through the tailnet if you don’t want to. Something tailnet nodes can do is serve the local subnet theyre connected to, even if you’re running the self hosted version Headscale, which is what I do. This is how I am able to have my phone and one other pc connected through Headscale/Tailscale, but still access everything on my local network.
Im assuming your Jellyfin is on your local network, and you want to connect to it through Tailscale, but still use HTTPS? If that’s the case, you don’t need to do any kind of port forwarding on your router, as everything is funneled through Tailscale anyway.
Hell yeah