DuckDNS/Lets encrypt stopped working - Please help

I’ve been using DuckDNS for multiple months and it has been working great. Initially I had some issues inside my network with it, but after changing configurations on my TPLink router, that was fixed. Yesterday I updated to 0.113 and it was working fine, but this morning I tried to log in and thought my server was down. I check with the local IP, no issues. So I decided to try from cellular, and still, won’t connect. I don’t see anything in the logs which tells me that I should be having an issue with it. DuckDNS appears OK, internal address hasn’t changed, port forwarding is still working.

Below are some logs. I do notice that there is an issue connecting to the updater. I am also experiencing issues with Google Home integration, but that is expected if duckdns is failing. Just not sure how to fix it at this point.

Any help would be greatly appreciated.

Startup log after reboot today.

2020-07-27 07:56:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for aarlo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-07-27 07:56:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for mail_and_packages which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-07-27 07:56:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-07-27 07:56:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for bond which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-07-27 07:56:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for badnest which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-07-27 07:56:16 WARNING (MainThread) [homeassistant.components.climate] ClimateDevice is deprecated, modify NestClimate to extend ClimateEntity
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of badnest is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of zeroconf is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of smartthings is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform template is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of denonavr is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform mail_and_packages is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of upnp is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.setup] Setup of harmony is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.climate] Setup of climate platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform soma is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.fan] Setup of fan platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform bond is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform updater is taking over 10 seconds.
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.components.light] Setup of light platform zwave is taking over 10 seconds.
2020-07-27 07:57:30 ERROR (MainThread) [homeassistant.components.updater] Timeout fetching Home Assistant update data
2020-07-27 07:57:30 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: zone, automation, smartthings, denonavr, mqtt, aarlo, zha, upnp, hacs, zeroconf, myq, neato, brother, badnest, abode, plex, harmony, timer
2020-07-27 07:57:32 WARNING (MainThread) [aioharmony.harmonyclient] 192.168.123.122: XMPP is not enabled, using web sockets however this might not work with future Harmony firmware updates, please enable XMPP
2020-07-27 07:57:32 WARNING (MainThread) [aioharmony.harmonyclient] 192.168.123.121: XMPP is not enabled, using web sockets however this might not work with future Harmony firmware updates, please enable XMPP
2020-07-27 07:57:41 WARNING (MainThread) [aioharmony.harmonyclient] 192.168.123.122: XMPP is not enabled, using web sockets however this might not work with future Harmony firmware updates, please enable XMPP
2020-07-27 07:57:41 WARNING (MainThread) [aioharmony.harmonyclient] 192.168.123.121: XMPP is not enabled, using web sockets however this might not work with future Harmony firmware updates, please enable XMPP

Log from duckdns:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[07:55:44] INFO: OK
75.52.159.57
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing bahome.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Aug 29 10:51:57 2020 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!
[08:00:48] INFO: OK
75.52.159.57
NOCHANGE

After numerous tests and failures, I’m thinking ATT changed something last night in their modem/router crappy thing and now I am struggling to get actual DMZ enabled, even thought it says it is. I had an internet ‘outage’ and I think it was a firmware updated to their modem. Not overly happy with them right now.

Have you checked your IP address is still valid in duckdns ? Your ip address may have changed and duckdns doesnt know about it.

So seems that it was definitely AT&T screw up, and some how my fiber line authentication was screwed up, but I still had internet. They said I shouldn’t have had internet even, so nice. All fixed, and can be closed.