2024-06-05, 11:12 PM
Hacks are extremely unlikely for us plebs. But there are a lot of things you can do to secure your setup. The problem is the learning curve.
The one thing I think you should do is go to DuckDNS and get a dynamic DNS address. You then install the DuckDNS client on your Jellyfin server and instead of using your IP you will use this DuckDNS address and the client you installed will automatically update the address if your public IP changes (which does happen on residential connections).
A lot of routers have a feature called "NAT loopback" or "NAT Hairpin". With that enabled your router will automatically keep traffic local if use your DuckDNS/public IP address while at home. Without it, when you use your public IP or DuckDNS address while at home, the traffic will go out to the Internet only to come right back. With NAT Loopback you avoid this and also don't have to switch between your public IP and local IP.
The one thing I think you should do is go to DuckDNS and get a dynamic DNS address. You then install the DuckDNS client on your Jellyfin server and instead of using your IP you will use this DuckDNS address and the client you installed will automatically update the address if your public IP changes (which does happen on residential connections).
A lot of routers have a feature called "NAT loopback" or "NAT Hairpin". With that enabled your router will automatically keep traffic local if use your DuckDNS/public IP address while at home. Without it, when you use your public IP or DuckDNS address while at home, the traffic will go out to the Internet only to come right back. With NAT Loopback you avoid this and also don't have to switch between your public IP and local IP.