I am setting up Home Assistant using HASSIO, and I am following
this to create the certificates:
addon installed with the following config:
files created in /ssl
core-ssh:/config# cd /ssl/ ls -l
-rw-r–r-- 1 root root 3574 Sep 6 21:55 fullchain.pem
-rw------- 1 root root 1708 Sep 6 21:55 privkey.pem
configuration.yaml file updated with the following:
Modem port forwarding: 80 >> 80 & 443 >> 8123
DDNS is done through -
Any help of what I might be doing wrong?
I don't know how that HASSIO works.
But checking your domain port 443 (your internal port 8123) is a http port (
Port 80 has a timeout. Port 443 answers with a typical error
The handshake failed due to an unexpected packet format.
So the tool checks, if port 443 works with http -> that works.
The same error is visible checking your port 8123 -
http answers with content, https answers with the same error message.
So there is one step missing: Your configuration doesn't know that 443 / 8123 should be a https port.
⚠ This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that. If your Home Assistant instance is only accessible from your local network, you can still protect...
Reading time: 3 mins 🕑
Likes: 1 ❤
A restart of Home Assistant is required for the changes to take effect.
Same if you use a Letsencrypt certificate.
Thanks for your detailed reply… I have seen a lot of tutorials and i think i did all the steps.
Below you can find a screenshot of a trace, and the PC from which I try to access the URL is returning an error “Protocol Version” if this helps.
This is the same problem. You have to find your "missing step".
Hi again … problem solved.
The default config that commes with HASSIO had an extra space character in the HTTP part of the config.
Thanks again for your help
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.