I recently attempted to set up the duckdns and letsencrypt parts of my HomeAssistant (want to use Amazon Echo), but the duckdns won’t redirect to HA, rather it goes to the router.
Secondly, I installed the LetsEncrypt certification- which does show up- but it is saying the following: (net::ERR_CERT_COMMON_NAME_INVALID)
How would I go about resolving this? I’m very new to the certification concept, but I can do the routing aspect easily. I have a Ubiquiti Edgerouter X.
What hostname is on the certificate? What address are you using to access HA?
If you are browsing to https://blah.duckdns.org, “blah.duckdns.org” must be on the certificate, either as the primary or as a Subject Alternate Name. If you use an IP or any hostname not on the certificate, you’ll get that error.
I am accessing the HA from my LAN address and the certificate has the address that THENAME.duckdns.org. But when I type that duckdns link it routes me to my router instead. I forwarded the port 443 to 8123 of the HA and it still does it. The hostname of the HA is actually HA and shows up as such in my ip scans and router logs.
I had this same issue with my Verizon FIOS router where it would take me to my router admin page instead of HA. I had to use advanced settings under Firewall > Port Forwarding so that I could get the option to set the Forward to Port section. I also was not able to set 443 as the source port, it had to be Any.
Awesome, I figured out that if I entered the doman link on the LAN it would forward me to my router, and if I entered the HA link on the LAN it would be unsecured. But when I remotely checked the domain link, HA did show up and with the certificate.
Does anyone know how to make the certificate installed and working on the LAN side of things?
Once you setup duckdns and lets encrypt you will always access HA using https://yoursite.duckdns.org even on your lan. You are most likely being taken to your router because 443 isn’t really forwarding to 8123.