a few days ago i just switched from Openhab2 to HassIO (HomeAssistant) because i like the WebUI in HA.
After i included all my devices into HA (stuff like Hue, Max!, Yeelight, Sonoff, etc.) im now trying to get external access to HA. There im still struggling. I installed DuckDNS, set it up at duckdns.org and afterwards i activated port forwarding in my router from 443>8123 and also 8123>8123. When i try to reach HA via https:// xxx . duckdns . org i cant reach it. Only by using http:// xxx . duckdns . org: 8123 it is working fine. But as i understand that there is no encryption when using http://…
I just want to encrypt the connection. So i try to deactivate the http: access and activate the https: access.
Can someone help me out with this?
Argh, thanks. Just found out that i had a second instance of “http:” at the bottom of configuration.yaml. There it was already https:…
Also i used the DuckDNS package which you linked in your earlier comment.
What do you mean with ‘’'? Should i add this to my yaml-File or here when posting some yaml snippets? Srr i dont get it yet.
After playing around and deleting the port forwarding except 8123>8123 (because it is told that you dont need port forwarding in the link above). After a restart i think i dont get any encryption files. The DuckDNS log tells me that:
Creating new directory /data/letsencrypt/xxx.duckdns.org …
Generating private key…
Generating signing request…
Requesting challenge for xxx.duckdns.org…
KO + Responding to challenge for xxx.duckdns.org…
KOUnknown hook invalid_challenge
ERROR: Challenge is invalid! (returned: invalid) (result: {
“type”: “dns-01”,
“status”: “invalid”,
“error”: {
“type”: “urn:acme:error:unauthorized”,
“detail”: “Correct value not found for DNS challenge”,
“status”: 403
},
“uri”: “https://acme-v01.api.letsencrypt.org/acme/challenge/xxx”,
“token”: “xxx”,
“keyAuthorization”: “xxx”
})
Sat Dec 16 14:26:23 CET 2017: KO
Sat Dec 16 14:31:24 CET 2017: KO
…
Do you know what the problem can be? Thanks a lot for your help.
Unfortunately not. The error code which is desplayed within mozilla is:
Fehlercode: SSL_ERROR_RX_RECORD_TOO_LONG
Edit:
Never mind. I got some help from a friend. He just found out that my base_url within the configuration.yaml is not within quotes “”. So now my setting is:
configuration.yaml
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: "xxx.duckdns.org:8123" # without https: but within quotes!
ssl_certificate: "/ssl/fullchain.pem"
ssl_key: "/ssl/privkey.pem"
ip_ban_enabled: True
login_attempts_threshold: 20