Cannot Access Server Outside of Home Network

[lakinreid]

The last few weeks I realized I've been having on and off issues with myself and my family connecting to my Jellyfin server while not on my home network. A few months back, myself and others had no issues connecting. Now recently, my sister has been getting the Cannot Connect To Server error when entering my domain name. Now after testing it on my cellular network, I am having the same issue. The only way it works on my phone/in the house is if I'm connecting directly to my home IP.. I note that as in the past I would see the server info contain my DuckDNS domain name.

I double checked that DuckDNS is up and running and it looks fine to me. It has my correct IP address and I have the yellow duck in my tray (which means it should be good). 

Other things that have changed in the recent-ish past: 
-Updated to Windows 11 (though that was 3 months ago, and issues didn't start then)
-Updated to Jellyfin 10.10.4, and just updated to 10.10.6 today to see if that fixed it, and it did not. 
-Moved and got a new ISP a few months back, but I have had many successful outside connections since then and the issues.
-hardwired my jellyfin server with ethernet, it was previously connected to my home network through wifi (not sure if that would of changed any settings)

Let me know if you guys have any thoughts, I'm honestly baffled. Everything was running smooth, and now POOF it ain't. Weird stuff. Thanks in advance yall!!

[TheDreadPirate]

Can you share your jellyfin log via privatebin.net? If you have an approximate time for the last time this happened, that would be helpful and sifting through your logs.

And what reverse proxy are you using? Also, did you setup port forwarding or are you relying on Jellyfin's automatic port mapping function?

[lakinreid]

Can you share your jellyfin log via privatebin.net?  If you have an approximate time for the last time this happened, that would be helpful and sifting through your logs.

And what reverse proxy are you using?  Also, did you setup port forwarding or are you relying on Jellyfin's automatic port mapping function?

Here are the logs from yesterday:  https://privatebin.net/?0b01d29fb7695b70#7QS6NM3HxEKR9tZj1p8trobGEstnASNuCc7Ti63mGUu3
I tried accessing it around 6-6:30pm on my cellular network, and again around 9-9:30pm. 

For a reverse proxy I am using Caddy.

In regards to the ports, it does look like Jellyfin is automatically mapping them. Though I do have 8096 as the local HTTP port number, though does that serve a different function than the Automatic Port Mapping check box? I've attached screenshots of my Jellyfin port settings so you can take a peek. Do I need to fill in any of the "Bind to Local Network address, Lan Networks, or Known Proxies" boxes? 

Also let me know if you are able to see what you need in the logs, I can always repeat my attempt to access my server from the cellular network, and then send the fresh logs with the exact time. 

Thanks!!

       

[TheDreadPirate]

Since you are using Caddy, you do NOT need automatic port mapping enabled. That setting will open ports 8096 on your router, which you are not using for remote access. At least I don't think so. When you connect from a remote client, are you using https://domain.duckdns.org? Or http://domain.duckdns.org:8096?

[lakinreid]

Since you are using Caddy, you do NOT need automatic port mapping enabled.  That setting will open ports 8096 on your router, which you are not using for remote access.  At least I don't think so.  When you connect from a remote client, are you using https://domain.duckdns.org?  Or http://domain.duckdns.org:8096?

So in the past I and my family was able to just type in domain.duckdns.org and it worked fine. Then the last few months I believe, only https://domain.duckdns.org would work. 

Though now I just tried the http://domain.duckdns.org:8096 and I was successful accessing the server from my cellular network!! I'm having a family member (one who was having issues) try it on there end in a bit, so hopefully that solves it. 

Any idea why the change in required address name happened over time? I did get a new router, modem, and ISP a few months back, would that have something to do with it?

Once again, I'm immensely grateful for your help!!

[TheDreadPirate]

Double check that port 80 and 443 are setup correctly in your router. If they are, it is possible that your ISP is blocking those ports.

Assuming your ISP is NOT blocking port 80 and 443, ideally you would remove port 8096 from your router's port forwarding. This forces all external connections to go through caddy. Going directly to port 8096 bypasses caddy.

You COULD use a different port entirely and route that to caddy. Most routers allow you to define an external port and redirect it to a different internal port.