Hi there,
My duckdns adress stopped working a while ago, and I worked around it by using the local ip while at home, but of course I want access via the app when I’m not home.
I can’t figure out what’s wrong and have tried following several other examples.
Ok, so it was working. Revert to that working configuration, restart the add-on and go to the duckdns.org website, sign in and check if the IP address there matches the public IP address of your router.
Hope the editing of the code worked, couldn’t really tell a difference…
The logs say a lot, but nothing related to the issue since I’m stopped before reaching HA (I suppose). Or is there any smart way of filtering the log?
Hi Tom,
Thanks for the reply. I didn’t change anything in the config, so reverting won’t help.
I did both restart and even reinstall duckdns, but to no avail. Both .pem file were succesfully created.
Regarding the IP, it is rather weird. The IP of the router and the duckdns aren’t the same, but if I change manually the duckdns addon changes it back.
Hi Tom -I found this useful, my routers WAN IP didn’t match the IP returned when I looked up my external IP Address. So duckdns was setting up the ISP address not my Routers WAN address. I found that my ISP had recently implemented CGNAT. I gave them a call and they switched it off for my account.