SOLVED: Recently Moved and now Can't Connect to Jellyfin Remotely

[lakinreid]

Good morning all! I recently moved and after getting my new internet all set up and running, but I cannot get my Jellyfin server remote access working.. I tried accessing it from my local wifi on my phone, and also on my phone with cellular data. It didn't give me an error or message, just the blank dark screen of the Jellyfin app. 

I'm a networking novice at best. Are there some obvious settings within Jellyfin or my network I must change? 

Some of my basic set up info: I'm using DuckDNS and Caddy to enable the remote access. Do I need a new DuckDNS url? Otherwise my router is a TP Link Archer AX1500, and my ISP is Midco (both are new to my setup). I confirmed that Jellyfin is working server side (no issues accessing it through Chrome on said PC). 

Any thoughts what might be happening? Thanks in advance!

[TheDreadPirate]

Did you update your DuckDNS address with your new public IP? Did you clear your app cache?

[lakinreid]

Did you update your DuckDNS address with your new public IP?  Did you clear your app cache?

Looks like DuckDNS is automatically updating my public IP address. I checked to see if it indeed did have the correct one, and it did. 

Just tried clearing my phone Jellyfin app, though it looks like there's no easy way to do that on the iPhone app.. (lovely) so I reset the app and also redownloaded it (as that was the suggestion on a different thread regarding clearing cache of iphone Jellyfin app). 

Restarted my computer, double checked that DuckDNS was working, started up Caddy, tried entering my server address on my phone Jellyfin app, but now it's just telling me "Could not connect to server". Triple checked the spelling of my server address, and it's the correct one.

[TheDreadPirate]

Did you setup port forwarding on the, I'm assuming, new router? Do you know if your new ISP uses CGNAT?

[lakinreid]

Did you setup port forwarding on the, I'm assuming, new router?  Do you know if your new ISP uses CGNAT?

You are correct, its a new router. Just set it up this morning! I have not touched the port forwarding yet. 

I did some looking into CGNAT, and I'm not 100% certain, but I'm pretty sure my ISP is not using CGNAT. Looks like my WAN IP wasn't falling into the range which apparently most IPs with CGNAT would be. I do have a Dynamic IP, not sure if that matters? 

So is port forwarding possibly the key to my issue then?

[TheDreadPirate]

Yes. Port forwarding is not optional. You have to setup port forwarding for port 443.

[lakinreid]

Yes.  Port forwarding is not optional.  You have to setup port forwarding for port 443.

Sweet, I will get that set up later today. Much appreciated as always!!

[lakinreid]

Yes.  Port forwarding is not optional.  You have to setup port forwarding for port 443.

Just confirming this indeed did the trick. Thanks again!