DuckDNS configuration

Configuration
1

I tried to use DuckDNS addon in Hass.oi.

  1. My addon config is:
    {
    “lets_encrypt”: {
    “accept_terms”: true,
    “certfile”: “fullchain.pem”,
    “keyfile”: “privkey.pem”
    },
    “token”: “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”,
    “domains”: [
    “xxxxxxxxxxxxxxxx.duckdns.org”
    ],
    “seconds”: 300
    }
  2. And i uncomment http section in configuration.yaml:
    http:
    base_url: xxxxxxxxxxxxx.duckdns.org:8123
    ssl_certificate: /ssl/fullchain.pem
    ssl_key: /ssl/privkey.pem
  3. I make port forwarding for 8123 port
    I copy xxxxxxxxxxxxx.duckdns.org:8123 in adress line my browser. And I see: “could’t connect”
    If i typing only xxxxxxxxxxxxx.duckdns.org i’m redirected to the web interface of my router.
    Please help me!!!
2

What if you type https://xxxxxxxxxxxxx.duckdns.org:8123/ in your browser?

By the way, you do not need to store secret information in your configuration.

3

I try https://xxxxxxxxxxxxx.duckdns.org:8123 but nothing changed((

4

Which works with your internal ip address? http://[ip address]:8123 or https://[ip address]:8123?
If the second one works, a certificate error is normal and expected.

5

Https works with internal ip, http not work

6

It is good https works. That indicates the DuckDNS addon is configured correctly.

Port Forwarding on your router would appear to be the issue.

On your computer, if you type nslookup xxxxxxxxxxxxx.duckdns.org do you get an ip address returned? If not that could be an issue too, but not too likely.

7

It returned ip address of my router -192.168.0.1. And next my external ip

8

It should show your external ip address.

9

It returned my external ip 90.xxx.xxx.xxx

10

Try a different browser? Sometimes Chrome’s caching behavior gets in the way.

11

Some routers do not support HAIRPIN NAT, so you may not be able to get to it.

12

I try it in Opera browser too, still not work. I check port 8123 in 2ip.ru, it displayed what port 8123 is opened