After setting duckdns following BRUH tutorial, I can’t access HA though hassbian.local/ or IP:8123. But when I type my duckdns.org site I’m able to go through to HA.
If I remove the HTTP configuration from the YAML config hassbian.local/ works again, but duck DNS doesn’t.
any thoughts?
Sounds like you have configured dns+letsencrypt, and the reason it “doesn’t work” like you say is that you get an error that the letsencrypt certificate doesn’t match.
Am I right so far? In that case this is the way it should behave.
When you get a certificate from letsencrypt, it is valid for that specific domain name. If you try to use it using the IP or the internal name it no longer matches those addresses.
So, how to fix it? You need to find a way to reach that ip using your duckdns.org address, even from the inside. How to do that will depend on what your network looks like, what kind of things your router can do.
As a starter point, search the net and this forum for dns rewrite and dnsmasq.
My setup is a Dlink wifi router LAN network, connected to the internet through a modem. I installed HA in a raspberry pi which is connected to the router with an ethernet cable.
This means once letsencryp and duckdns is setup I can only access HA through my_address.duckdns.org?
If it connected to my local network, shouldn’t I be able to access HA through hasbian.local or IP?
Thanks for the help. I will search for what you suggested.
That depends on if your browser will let you access a site with an invalid certificate or not, since the cert is valid for my_address.duckdns.org, but not hassbian.local or the ip address itself.