HA and DuckDNS

Configuration
1

Hi all,

Sorry in advance if this has been covered and my search skills did not bring me to the right thread. Totally new to HA and have been struggling getting duckDNS to work for a few days now. After installing the Duck DNS add on and configuring it, configuring my router to port forward, and making the changes to the .yaml, I still cannot get it to work correctly.

I can no longer access HA though https://homeassistant.local:8123/ just get a page not loading in browser
I cannot access HA though https:myduckdnsdomain.duckdns.org or /8123, - get a “Unable to connect to Home Assistant” Screen

Now if I go to DUCKdns.org and after logging in change my “current ip” to my PI ip, I can now connect to HA until DUCKdns reverts back to my external IP.

I apologies in advance if this is something obvious but I am a networking rube

2

First, it is going to be https.

Did you add the security certificate information to your configuration.yaml file?

3

Did you try https:myduckdnsdomain.duckdns.org:8123 ?

Which port did you forward? I supposse you configured the access token etc…
I can access HA through https:myduckdnsdomain.duckdns.org:8123 but not trough http://homeassistant.local:8123/ , depends on your configuration and your router.

1 Like
4

Thanks for the response,

the http was a typo, edited and corrected.
Below are the changes made to .yaml

http:
  base_url: https://mydomainhere.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
5

Hi thanks for your reply

I forwarded ports 8123, 80, and 443

6

Base URL is depreciated. Please remove it.

7

You only have to forward one port. Otherwise the router doesnt know which port to forward.

8

Ok so just:

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

Done.

9

ok deleted all but 8123.

10

Still seeing same thing. No access from outside of network, and “unable t o connect to home assistant” unless I change the IP to local IP of PI in duckdns.org

11

Maybe your router doesn’t support hairpinning (NAT loopback).

Try from a device not connected to your local network (mobile phone with wifi turned off).

12

I have an asus router and from the googlefu I did it seems that it does. In either case I am not able to access though a phone I tired that, get a server not responding message. Don’t even get the unable to connect to home assistant splash screen.

13

Does the public IP address of your router match the IP address on the duckdns page (before you change it)?

14

It does not, Thank you for pointing this out, looks like I need to call my ISP.

15

Yep, sounds like your ISP is using CGNAT which is incompatible with dynamic dns services like duckdns.

If they want to charge you more than $5 for a non CGNATed address just use Nabu Casa instead. It works with CGNAT.

16

OK everything is working now. Thanks you so much for all the help. I am an idiot, the modem was not set up in bridge mode. Everything is working now!!