Just run it on the LAN and don’t expose it to the Internet.
This would require paying for a VPN to allow LAN connections, which is an option but not my preferred one.
HTTPS only secures the connection, and I doubt you’re sending any sensitive info to or from Jellyfin
This is a matter of threat model, and I would prefer not to expose my TV preferences unencrypted over the network.
but you can still run it in docker and use caddy or something
Does Caddy require a custom DNS in order to point the domain to a local IP address?
The bigger target is making sure jellyfin itself and the host it runs on are updated and protected.
This is easy with securecore, since it updates daily. The rest of the semantics for the actual hosting side aren’t too difficult.
catloaf@lemm.ee 1 year ago
You don’t need a VPN for LAN connections. You’re already on the LAN. You’d only need it for access from the WAN.
If you’re using Let’s Encrypt, you should probably purchase a domain. I don’t think they support .internal domains. Or you could set up your own CA and run it however you want, even issuing certs to access by IP address if you wanted.
Charger8232@lemmy.ml 1 year ago
ProtonVPN by default blocks LAN connections, and can only be changed using their paid tier.
catloaf@lemm.ee 1 year ago
For that aspect, I would recommend changing to a provider that doesn’t have such ridiculous restrictions.
AbidanYre@lemmy.world 1 year ago
I kind of get it from Proton’s POV. If they have a free tier that allows a limited number of devices they’ll want to make for you don’t tunnel all you devices through that one.
Charger8232@lemmy.ml 1 year ago
The only other providers I would use are Mullvad VPN or IVPN, both of which are paid.