It’s been about 3-weeks of struggling in the evenings to get DuckDNS configured so I can use an SSL connection. I’ve poured over countless other posts with issues that were related to what turned out to be simple configuration issues with either Configuration.yaml file or DuckDNS configuration. I can’t seem to find any commonalities in my case, so some help would be greatly appreciated. When installing DuckDNS, I get confirmation in the DuckDNS log that it completed successfully and can see the public and private key files located in my /ssl directory on my RP3. I’ve confirmed that DuckDNS is seeing the correct IP address that my ISP has provided me and when I try using my cell phone, with Wi-Fi disabled, to hit my public IP address, the only way I can successfully connect to HA is by using http://my_public_IP:443. If my public IP were 123.45.67.89 then here are the results of various tests:
https://123.45.67.89:8123 - ERR_CONNECTION_TIMED_OUT
http://123.45.67.89:8123 - ERR_CONNECTION_TIMED_OUT
https://123.45.67.89:443 - ERR_SSL_PROTOCOL_ERROR
http://123.45.67.89:443 - connects unsecurely!
https://123.45.67.89:80 - ERR_CONNECTION_REFUSED
http://123.45.67.89:80 - ERR_CONNECTION_REFUSED
My Configuration.yaml files looks pretty simple at the moment as my system recently crashed and I started all over again. It looks like this:
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
base_url: my_subdomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# Sensors
sensor:
# Weather prediction
- platform: yr
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
My DuckDNS config looks like this:
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "my_personal_token_from_DuckDNS",
"domains": [
"my_subdomain.duckdns.org"
],
"seconds": 300
}
I have a double router configuration with R1 at premises and R2 wired to LAN of R1. On R1, I currently have the following port forwarding rules: 8123->8123, 443->443.
On R2, I currently have the following port forwarding rules: 443->8123, 80->80.
I’ve tried moving my RP3 to LAN of R1 to eliminate potential issues with a double router config and added the port 80->80 and 443->8123 rules to R1 but with similar results as shown above when trying various combinations of http/https with my local IP address and various ports. Don’t know what else to try… A little help please!