You don't need to hard update your IP every 5 minutes. The typical DNS updaters (just use ddclient) can simply check if your IP is up to date and only update if it isn't.
post
I still don't recommend putting jellyfin on the Internet. It's not designed for it. There are some API endpoints you can access without authentication, not to mention potential authentication bypass vulnerabilities.
5 minutes is also probably too frequent. Leases are usually significantly longer. You might hit a rate limit and get blocked.
If it's for your personal use and no one else is going to connect, why don't you just configure a wireguard tunnel to remotely connect to your server as if you were in LAN without exposing anything?
I’d like to be able to share it with friends and family
Tailscale has the Funnel feature too, which puts the endpoint on Tailscale's servers.
You could do both - Funnel for people who you don't want to walk through setting up a client, and use the client for those who you're willing to put the effort into.
Tailscale allows you to do the same except you can create keys with limited access to only certain ports (just in case you don't want them peeking around your server).
Meh, I won't expose ports anymore - last time I did I had someone hammering on it hard enough to slow my consumer router.
I closed the port and would still have someone hammer it occasionally for months, hoping the port was still open.
Just for my own education, if you don’t mind - how were you able to tell someone was hammering on the port if it was closed? Would fail2ban have been an option to stop them?
Haha okay, thanks! And I’d just forward ports 80 and 443 from the router to ports 80 and 443 on the Pi’s internal IP address in the router settings, right?
It's perfectly fine to host jellyfin online. Use a proxy server to enable TLS and do not use default ports 80/443. Use letsencrypt for free certificates. No need for VPN to access here either. Do not expose any other ports such as SSH on default ports. Lock down your jellyfin server and any other related services behind a VPN service and block access to Internet through other interfaces (except for port forwards on your ISP for jelly). Go high on port ranges since they typically aren't scanned or blocked. Go dual stack for best results and don't use your router address for IPv6 more than likely you have your own /64 choose a different address for port forwards. Do not assign this address to your internal servers. Use a reserved unrouted IPv6 range internally and do NAT6. Do not allow any raw IPv6 internet access
do not use default ports 80/443.
In my opinion, you'd be fine using default ports. Guess there's no harm in using other ports though, other than the pain of having the remember which port to use if you ever forget when adding a new device, etc.
Edit: I should add that im speaking of only ports 80/443 here. If you must expose ssh over the internet (probably shouldnt) for example, then yes, use a non-standard port (I use non standard ports for pretty much all apps except http/s).
Do not expose Jellyfin. It has unauthenticated endpoints that will be exploited by bots
top 34 comments