DuckDNS with Lets Encrypt no longer works after adding router

I have AT&T Uverse as my internet provider and am forced to use their gateway which also has a router built in. Last weekend, I added a Netgear Nighthawk AC2300 behind the AT&T gateway & 99.99% of my internet activity works except DuckDNS. I have done the following:

  • removed any Hassio port forwarding from ATT gateway & added to the Netgear router. Turned off gateway WiFi.
  • put AT&T gateway in “DMZplus mode”, which is the closest the gateway has to bridge mode & select the Netgear router as the device. It reports all applications, ports & protocols are being sent to the netgear router.
  • Public IP on gateway matches what netgear says is it’s IP address & this also matches what DuckDNS website says is my current IP.
  • removed port fowarding on netgear router & tried all combinations of 443 & 8123 on the external & internal ports.
  • uninstalled DuckDNS & reinstalled with same config.
  • DuckDNS logs are clean/green & reports same IP as the DuckDNS website, gateway & router.
  • Hassio/Supervisor logs are clean/green too.

Luckily, I can still access my Hassio instance with hassio.local & Nabu Casa cloud on Win 10 chrome browser, & both the iOS & Android HA app (local & remote). But, I can’t get DuckDNS to work. Does anybody have any suggestions?

Thank you.

1 Like

same issue here.

were you able to fix it ?