+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Remote access (/t-remote-access--11473)
Pages:
1
2
RE: Remote access - TheDreadPirate - 2025-04-02
A thought occurred. Since you mentioned that your IP did NOT change, I remembered that some ISPs block port 80 and 443 on residental Internet plans. Their justification being that "only businesses need to run a web server".
Try using a non-standard port for the "external" port.
Something like this for the port forwarding rule
external port = 50080 -> internal port = 80
external port = 50443 -> internal port = 443
When you're remote you'd have to add the port to the end of the address. https://jellyfin.domain.tld:50443. NAT Loopback should handle this gracefully as well.
Your ISP blocking port 80 and 443 makes more sense than CGNAT. From other users here that did have CGNAT, they just straight up did not have the ability to setup port forwarding on their ISP provided router.
Regarding setting a cutom DNS entry, IP Alias doesn't look like what we need. And the manual I could find for a router in the same family wasn't much help. If it was accurate, you cannot set a custom DNS entry.
RE: Remote access - carlospj - 2025-04-02
(2025-04-02, 08:07 PM)TheDreadPirate Wrote: A thought occurred. Since you mentioned that your IP did NOT change, I remembered that some ISPs block port 80 and 443 on residental Internet plans. Their justification being that "only businesses need to run a web server".
Try using a non-standard port for the "external" port.
Something like this for the port forwarding rule
external port = 50080 -> internal port = 80
external port = 50443 -> internal port = 443
When you're remote you'd have to add the port to the end of the address. https://jellyfin.domain.tld:50443. NAT Loopback should handle this gracefully as well.
Hello again,
OMG, this is working! I finally have remote access to Jellyfin!! It was the blocking thing for sure!
Although I have a couple of questions.
Is it right the ports 5080 and 5433? Because the ports you put gave me an End Port Range error.
An second question. I still don't have access to jellyfin with the URL in my Local Network. Is there a solution for that or I should use the LOCAL_IP:PORT to access it? Do I have to change something in cloulflare, npm or the docker compose? Maybe the JELLYFIN_PublishedServerUrl variable?
Thank you for all your help!
RE: Remote access - TheDreadPirate - 2025-04-03
Ideally you use a port in the "ephemeral" range.
https://en.wikipedia.org/wiki/Ephemeral_port
But if your router doesn't let you, I guess any port above 1023 will have to do.
I was thinking back to when I was still using NAT loopback. I THINK I had Nginx running on the same port that I was port forwarding.
So you may need to configure the Nginx Proxy Manager container to uses ports 5080 and 5443 and redirect them to 80 and 443, respectively. That would look like this if you are using docker compose.
Code:
ports:
- 5080:80
- 5443:443
- 81:81 #nginx proxy manager mgmt portThis should fix access will on your LAN.
RE: Remote access - carlospj - 2025-04-03
So, about the ports. I was having trouble to use 50080 and 50443 because I was editing the existing rules, and apparently, my router didn't like that. But I thought of creating two new entries and tried it and my router let me do it without complaining, so I'm using ports 50080 and 50443 as you suggested in the previous message.
And for the NPM ports, I tried what you said of changing the default ports in NPM, but it didn't work, both without putting the port at the end of the URL, and a bookmark I had in the browser saved with the URL+port. However, I tried to put it by hand with the port at the end of the URL and once I did that, it started to work. I could have sworn that in the bookmark I had the port set correctly, but I don't know.
So I said to myself, maybe it was just the port thing and I don't need to change the NPM ports, so I tried it and indeed it works like that too. Putting the port in the URL works in my Local Net.
So right now I have everything working perfectly, both locally and outside my network.
Thank you so much for all your help, I couldn't have done it without it.