SOLVED: Changed from Static IP to Dynamic

[thedailyflannel]

Hello! So I know this is my own fault. I shouldn't have rocked the boat. I finally got Jellyfin connected and everything was working. I have Jellyfin running in a Docker container and I use Dynu DDNS, a domain, and Nginx proxy manager. It was all good. But in the set-up process I had set everything up manually with Caddy and Jellyfin originally, decided to use Docker instead, uninstalled Jelly and Caddy, installed Docker, changed reverse proxies, etc.

So I was double-checking everything this morning and realized that since I have a DDNS, I shouldn't need a static IP, right? I had set one up in the initial chaos when I was manually downloading Caddy and Jelly. But the point of a DDNS is to not have a static IP, no? So I turned off the static setting in my network settings and double-checked. My public IP is the same regardless right now, and it's that public IP that my domain is pointed at.

As far as I can tell, what I did shouldn't have knocked the tower of precarious cards over... except now my domain doesn't connect to the server and the local host for the Jellyfin port also says it can't connect. Is there a setting I need to find a way to tweak somewhere? Do I in fact need to have a static IP? Should I just put it back and back away slowly before I ruin it all?  

Any advice is so appreciated!

[TheDreadPirate]

What static IP did you disable? The WAN IP or the LAN IP? If it was the LAN IP, did your server's local IP change and now the port forwarding rule is sending to the previous IP?