I have had DuckDns, working with “HTTPS:” on previous version of Hassio up to 0.71.0, on a RPI3.
At Hassio 0.71.0, I decided to start learning to work with InfluxDB. While settting InfluxDB up, I did something wrong, and hosed Hassio. So I reloaded from scratch, first the basics,
- Samba Share,
- SSH Secure Shell,
- Mosquitto broker,
ALL the above, seems to be working fine locally, then I tried to setup DuckDNS, and no joy… I have installed it on previous versions of Hassio with no issues. But, now, no matter what I do, I cauld not get “my_Domain.duckdns.org” or “https://my_Domain.duckdns.org”, to work.
This is what I have for the code in the DuckDNS Addon:
{
"lets_encrypt": {
"accept_terms": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "Cut & Pasted from DuckDNS Directly",
"domains": [
"my_Domain.duckdns.org"
],
"seconds": 300 # Set DuckDNS to check every 10 minutes for testing.
}
And this is what I have in the Hassio Config.yaml file:
http:
api_password: !secret ha_api_pwd
base_url: !secret ha_base_url1
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
ip_ban_enabled: true
login_attempts_threshold: 5
With SSL turned OFF, like above, I could access Hassio, using “IP address:8123” locally ONLY.
When I re-configured DuckDNS Add-on with, “accept_terms”: true,, and removed the two “#” from the ssl lines. I could ONLY access Hassio from an External IP Address, using HTTPS://my_Domain.duckdns.com, I was unable to access Hassio locally, with either IP Address or DUCKdns.
Well, after about 12 hours or research and tinkering, I found, and only chance, in my Router’s Security section. There is an option to, “Filter ReDirects”, after turn off the filter(unchecking it). I could once again, access Hassio, using HTTPS://my_Domain.duckdns.com, from both internal & external IP addresses…