I wasted probably 5 hours trying to enable letsencrypt through the addon which shouldn’t even be in hassio anymore as all you have to do is change the “accept terms” flag to true in the duckdns addon page. I finally uninstalled the letsencrypt addon in hassio. duckdns created the .pem files, finally, but when I add
Duck DNS
{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “myToken”,
“domains”: [
“mySubdomain.duckdns.org”
],
“seconds”: 300
}
Config:
http:
base_url: mySubdomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
api_password: myPassword
If I comment out the ssl_cert line and the ssl_key line, hassio will boot. If I don’t comment out those two lines, hassio will not even load, I can get into configurator but home assistant front-end wont load.
forwarding 443 to 8123 doesn’t help.
adding back port forwarding 8123 to 8123 doesn’t help.
forwarding 443 to 443 doesn’t help
forwarding 80 to 80 doesn’t help either.
Why are those two lines that are needed for SSL causing hassio to not boot?
Now I just realized i’m unable to load hassio from my duckdns address. ugh
when I restart the duckdns addon it says i’m good:
- Checking domain name(s) of existing cert… unchanged.
- Checking expire date of existing cert…
- Valid till Apr 27 05:37:52 2018 GMT (Longer than 30 days). Skipping renew!
using my public ip address with the 8123 port doesn’t work now either.