You’ll also need to do some port forwarding at the home router level so that external users can reach the server.
You’ll preferably want to do what’s called a DHCP reservation so that your server’s internal IP address remains the same, then do a port forward from your public port 8096 to internalIP:8096. That way, you just have to point someone outside of your network to hostname.duckdns.org:8096 (which will get resolved to your current public IP address) for your Jellyfin server.
Someone already suggested that but it seems to be missing a step, still need something to direct to the port I have for jellyfin?
You’ll also need to do some port forwarding at the home router level so that external users can reach the server.
You’ll preferably want to do what’s called a DHCP reservation so that your server’s internal IP address remains the same, then do a port forward from
your public port 8096tointernalIP:8096. That way, you just have to point someone outside of your network tohostname.duckdns.org:8096(which will get resolved to your current public IP address) for your Jellyfin server.tried doing hostname.duckdns.org:8096 and it didnt work so Im not sure its supposed to be like that, website mentions something called caddy
you’ll need to have your own hostname and make it point to your home IP address, just in case it wasn’t clear enough
It’s good you are trying to help but I’m not sure someone copying and pasting whatever they read should have a port exposed to the Internet.