Hi,
There are many other similar topics raised in the past, but as the HA releases evolve, they didn’t help me. So I thought it would be good to get some updated help, which could help also others.
I have a fresh 0.115.6 HA installed on rpi 4, and I have successfully installed and enabled duckDNS. The duckDNS logs show succesful certificate signing requests and certificates are in place (I can see them from SSH). duckDNS works because I’m able to access HA with HTTP from the internet, using the subdomain I created.
The problem is HTTPs.
I have seen both forwarding to 8123 and 443 for the https service in the forum, so I’m trying both. I’ve set up the following port forwarding rules in my router:
65020 forwarded to rpi’s 443
65021 >> >> 8123
http://<mydomain>.blackduck.org:65021 Works, I get to login screen
https://<mydomain>.blackduck.org:65021 I get ERR_SSL_PROTOCOL_ERROR
on firefox: SSL_ERROR_RX_RECORD_TOO_LONG
https://<mydomain>.blackduck.org:65020 I get ERR_CONNECTION_REFUSED
So I assume 8123 is the correct port to forward to, because it seems to reach further on the SSL level.
I’ve tried using other browser or cleaning the cache, it didn’t help.
I also tried adding the ‘base_url’ in configuration.yaml under http, but the HA core failed to start, because base_url is a deprecated prameter as the logs said. So now I have no http: config in the configuration.yaml.
This topic seems similar but resolution needs the deprecated base_url config
Any ideas how to solve?