It seems Duckdns has been somewhat unreliable lately, and I was thinking it would make sense to use my local IP to access HA instead of https://xxx.duckdns.org. But I’m getting the same behavior as the OP.
Is it possible to access HA using my local IP (https://192.168.1.101:8123) in my internal network while using the duckdns DNS externally?
Having same issue, seems duckdns is down.
Checked again and it’s back up, all seems to be working.
"Hi all, brand new to all of this so was following video guides but I am having same issue.
DNS_PROBE_FINISHED_NXDOMAIN
I had it all working, on Raspberry Pi, added duckdns, next stage was to integrate google assistant however! It would not let me log in through my local network anymore, only though the DNS. So I tried to delete everything off the SD card, flashed the SD card again with The Rasp Pi OS and then Home assistant OS, removed the port forwarding from my router hoping this would start all over again. Since then I have managed to flash Home Assistant onto the SD card and it loads to login but when I try to do so it just gives me an error message. And now I cant access Home Assistant at all.
Does anyone know a fix?
Thanks
I’m able to access hass locally and via duck dns w/o any extra steps. I’m using https:// to access hass. Hope this helps.
I’m also struggling and I really can’t figure out why.
My DuckDNS configuration is:
lets_encrypt:
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: my-actual-token
domains:
- my-actual-domain.duckdns.org
aliases: []
seconds: 300
I have setup port forwarding from 8123 to the internal IP at port 8123.
I’ve added the following to my configuration.yaml … but as soon as I un-hash these lines I’m not able to access HA by my local (IP:8123 or homeassistant.local:8123) … nor by my specified DuckDNS domain.
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: true
login_attempts_threshold: 5
I’ve checked the configuration in Server Controls and it’s valid. Would really appreciate some help with this as the Pi is going in the bin if I can’t get it to work!
Just reading around… I’ve checked the SSL on SSLChecker and it’s reporting:
No SSL certificates were found on [[duckdns-domain]]. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server’s firewall.
Any idea why?
You’re using the wrong ports in your port forwards.
Forward port 443 to 8123 and don’t put the port number on the end of your duckdns url.
You should use your duckdns url when inside your network too, but if you must use local access then you must use https://your.ip.address:8123 (note the S!) and accept the security warning.
Hi thanks for your answer. I’ve seen so many conflicting/confusing posts and videos on the port forwarding.
I’ve tried forwarding 443 to 8123 and not putting the port number on the end. In this situation I get forwarded to my modem’s config page.
Then your router/modem is not configured correctly.
Are you certain that’s the culprit? It seems there’s something weird going on with the SSL Certificate. When trying to access using the mobile app I get the message “The certificate for this server is invalid”
The certificate will only be valid if the address typed into the url bar matches the address on the certificate for the page(s) that are viewed in the window.
If you are accessing locally ‘192.168.1.254’ does not match ‘my-amazing-homeassistant.duckdns.org’, for example.
If you are accessing remotely, but you are getting your router’s configuration page, again it won’t match, because presumably your router’s configuration page uses a different certificate to the one you generated for your homeassistant installation.