Awesome, thanks for the tips!
Comment on Plex has paywalled my server!
sudo@programming.dev 2 days agoBut I ran into challenges getting my server safely accessible for users outside my LAN
FWIW:
- vps + domain (optional?)
- connect vps to home server with wireguard (eg Tailscale)
- reverse proxy on the VPS forwarding to jellyfin (eg Caddy)
Obviously not as trivial or seamless as Plex. Also I wouldn’t try to complicate this setup by using docker for everything. But once its up you can basically host whatever you want on the WAN from your LAN.
ThePowerOfGeek@lemmy.world 2 days ago
tehn00bi@lemmy.world 2 days ago
So an additional 10 bucks a month….
sudo@programming.dev 2 days ago
5 actually because you can use minimal hardware. You can probably just port forward your router and run caddy on the same jellyfin server but then expose your home IP address.
foggenbooty@lemmy.world 2 days ago
What added security do you get by using a VPS besides obscuring your home IP? I can definitely see benifits to not leaking your home address, but otherwise the reverse proxy and wireguard tunnels don’t actually add any increased security for the extra steps. You could just host a reverse proxy at home, and any flaws Jellyfin could have in their app would still be exposed.
I’m not knocking your solution, I’m just in a similar place and considering if I want to go through the extra hurdle for a VPS if I don’t need one.
sudo@programming.dev 2 days ago
Obscuring home IP is the big one. You also don’t have to fiddle with opening ports on your router and maybe getting ISP attention for hosting on a residential network. But really obscuring home IP address would work.
Dirt simplest solution is caddy on the same jellyfin server and port forward 443 and 80 on your router to that host. Hopefully letsencrypt will work without a domain but I’m not sure.
foggenbooty@lemmy.world 1 day ago
That’s basically what I do right now except I do have a domain and my ISP doesn’t restrict inbound ports like 443 so it works fine.
Just trying to sort out if I want the headache of a VPS if I don’t need it (costs, maintenance, point of failure, etc).
sudo@programming.dev 1 day ago
Sounds like you don’t need the VPS then. Add a subdomain to your home IP. Port forward 443 and 80 to the sever. Run caddy to route the subdomain to localhost:8096. You will also need to tell jellyfin to accept on the new domain.