I can never go back, I can see why torrenting is so popular in Canada

KuroeNekoDemon@sh.itjust.works to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 881 points –
167

You are viewing a single comment

Someone already suggested that but it seems to be missing a step, still need something to direct to the port I have for jellyfin?

That's just on your router, no?

no idea, I dont know how to do any of that

This tutorial explains everything in detail.

Edit: I stupidly assumed you are using windows. But anywayys...if you are thats a good tut

I am on windows, your stupidity paid off. Hooray stupid but lucky people! (sadly Im only stupid, not lucky)

Followed that guide and only managed to make my duckdns domain lead to my router...

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.

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

1 more...
1 more...
1 more...
1 more...