Url is not reachable newly created domain after enabling publicIP with duckdns

Hello All ,

Before I ask , I would like to mention I did really gone though the community posts for the solution.

What I have done:

I followed the guide to setup duckdns and configuration on HA. His video has been recommended on HA startup page.

Issue I am facing:

After following the guide, I am unable to access HA from https://XXXXX.duckdns.org

Steps I have followed and configurations:

As mentioned I have followed the mentioned guide and set up as-is.

duckdns - addon configuration -


lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: XXXXXX
domains:
  - XXXX.duckdns.org
aliases: []
seconds: 300

configuration.yaml


#uncomment this if you are using SSL/TLS, running in Docker container, etc. 
http:
  base_url: xxx.duckdns.org
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: True
  login_attempts_threshold: 3

port forwarding from my router. This is centurylink.
chrome_KKaQqXdMhF

as this isn’t showing completely, here is the setup page before clicking submit. And I have tried alerting the ports as well.

expectation is when I hit the URL https://xxx.duckdns.org I should get the HA’s login page. I have been getting as
Also, I am unable to use local IP as well

This site can’t be reached

I have even followed this excellent community reply of someone who faced similar issue, but no luck.

Some of other checks I did:

my modem isn’t cg-nat enabled - I have confirmed by finding the IP coming from here and on my modem login page the IP it is showing. This shows that the WAN IP-address is OK and thee ISP isn’t using CGN. – please confirm if my understanding is wrong.

I have verified whether 443 port is exposed or not on https://canyouseeme.org/

Success: I can see your service on xxx.xxx.xx.xxx on port (443)
Your ISP is not blocking port 443

by removing the config from configurations.yaml(luckily I have ssh setup already done) the site is back online and available to under locally. Which confirmed me clearly some issue with port forwarding or duckdns config/setup.

one thing I wanna mention, is I am new to HA and just setup HA on pi4. But I am using non stable version. If that need to be considered.

~ $ ha os info
board: rpi4-64
boot: A
version: "5.3"
version_latest: "4.15"
~ $

Thank you for reading this, if you can help me here would be really great.

Hi @uniquecool,

Having the same issues! have you managed to solve this?

Thanks!
Didi