SWAG (Let's Encrypt) no longer working with NextCloud

Last month, I committed the cardinal sit of IT by changing two things at once. I upgraded my router (from an Unifi USG Pro to a Unifi Dream Machine) and upgraded my Unraid cache drive at the same time. During the cache drive update, I had to rebuild my docker image, but was mostly successful in getting everything working again.

The only thing that I can't get working is my reverse proxy (I use SWAG, previously known as "Let's Encrypt").

I really only use SWAG to manage the reverse proxy connection for NextCloud (which I use to host files and give my friends/family an easy to access page for sharing files/photos) and BitWardenRS. Prior to these upgrades, everything worked just fine.

I use duckdns and have confirmed that the IPs were updated in the duckdns portal (my external IP did change when upgrading the router).

Symptoms:

When I try to launch Nextcloud via the WebGUI, it takes me to MYNEXTCLOUD.duckdns.org/login - which does not work (refused to connect).

When I try to launch Nextcloud via the internal IP address, it automatically routes me back to the MYNEXTCLOUD.duckdns.org/login (which failed because it refuses to connect).

I have my SWAG and NextCloud dockers both set to use the "bridge" network.

I'm not seeing anything in the logs that make me think it's not working correctly.

Interestingly, BitWarden will work when using the internal IP, but fails the same way (refused connection) when using the reverse proxy via SWAG.

Additional information:

I am using port 444 for my NextCloud docker.

I am using version 28.0.0 for NextCloud I have tried in both Chrome and Firefox My nextcloud iOS app will not connect (it uses the duckdns external portal).

Any help would be appreciated!