DuckDNS URL no longer working

Configuration
1

I haven’t made any updates or changed any configurations, but now my url “mydomain.duckdns.org” is no longer working. If I’m away from my house I can access HA using my WAN IP (xx.xx.xxx.xxx:8123), however, using “mydomain.duckdns.org” no longer works. Even if I’m on my LAN I can’t use my DuckDNS URL.

DuckDNS Config

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "33ebacf6-d211-48c8-b3f5-xxxxxxxxxx",
  "domains": [
    "mydomain.duckdns.org"
  ],
  "seconds": 300
}

DuckDNS has my correct WAN IP Address.

I kind of suspect this has something to do with my Let’s Encrypt certificate, but I can’t find out how to see if it is active. I’m using the DuckDNS built in Let’s Encrypt cert. Any idea where I should look to fix this?

2

Hi,
I had similar problem, solution for me at least is in this thread: Bizarre UI Access Issue

Hope it works for u aswell.
All though i still have some problems accessing through duckdns sometimes, for me it works to just refresh a couple of times. But that only worked after the change that i mentioned just above.

3

Thanks. I’ll take a look at that

4

Unfortunately, nothing on that other topic helped me. I still have the problem. I tried restoring back to a version 3 days ago when I know it worked, that didn’t fix it either. I have tried uninstalling DuckDNS add-on, removing Nginx, and using the DuckDNS component with LetsEncrypt add-on. None of it has worked.

5

I figured it out. I don’t know when or how, but for some reason I had removed my 443 port forwarding in my router. I was working on some Blue Iris HTTPS stuff a couple nights ago and must have inadvertently done it then. I’m seriously mad at myself that it took me this long to figure this out.

Lesson learned, no more bourbon while working on networking. :slight_smile:

6

Good you found the reason :slight_smile:
Change to rum and try again, usually works for me, haha :wink: