I had this same problem with my installation (pi) . But I don’t remember exactly what the fix was. Either I had a missing http: in configuration.yaml or the SSL port was forwarded to the wrong IP.
I would try to use standard port 43 for https
just leave out the 8123
base_url: https://.duckdns.org
And forward port 43 to 8123
Hi Windsurfer,
That is not my case. Not worried about router publishing for now. Even internally I am unable to access homeassistant frontend using https on port 8123
OK, I am with you. a problem with the certificates ? … maybe someone running a docker can chime in.
Certificates are OK. They are used in other addons like IDE without any issue.
After some more fiddling with configuration and still without luck, I came across with this when running command: hassio ha info
core-ssh:~# hassio ha info
arch: amd64
boot: true
custom: false
image: homeassistant/qemux86-64-homeassistant
last_version: 0.87.1
machine: qemux86-64
port: 8123
ssl: false
version: 0.87.1
wait_boot: 600
watchdog: true
The entry ssl:false seems to be the problem. As far as I know this should be set to true but I do not know how to do it.
Anyone?
Thank you all.
Solved my issue.
In my configuration.yaml, the http: header was under config: header, instead of being at the same level.
It was a fresh install so something went wrong with the template or I did some change that I did not notice and the result was SSL not working.
Thank you all for taking time trying to help.
7 Likes
Thank you Xptorol for posting your fix!!! I had been staring at my config for a day… then with your post realizing I was doing the same thing where I had " http:" rather than “http:”… I was starting on the second column of line rather than on the first.
Thank you!
Rich
You made my day:grinning:, I had been struggling with this for a week now, I was about to re-install my home assistant…
Thank you!! Had the same issue " http:" instead of “http:”. Took me 2 days to figure out.
mates:
can i peep at your configuration. yaml?
Its has been 2 weeks, I’ve tried but with NO success.
Thanks
@Ajaxhan_Anna My working config 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: https://changetoyours.duckdns.org
server_port: 8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# Text to speech
tts:
platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
2 Likes
This answer helped me.
Changed address (ofc)
Changed port to 443
Created port in/out 443 in router.
Maybe I could have left it at 8123 inside my network, but this works for me.
Thank you for posting your fix. Had the same problem
Duckdns and SSL running now!
Thanks,
Boris
Thanks a lot, this was exactly my issue!
Thanks it help me out
These are my configuration.yaml lines:
http:
base_url: https://ottoha.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
If i try to connect to the duckdns domain from inside the lan or from outside (using a phone with wifi off) this is what i get:
Il sito non può fornire una connessione protetta
ottoha.duckdns.org ha inviato una risposta non valida.
- [Prova a eseguire lo strumento Diagnostica di rete Windows](javascript:diagnoseErrors()).
ERR_SSL_PROTOCOL_ERROR
I’m novice with HA, is there anyone who would put me on the right track? THANKS
Ugh, I didnt know YAML worked like that. Thanks for the solution.
I have been staring at this for days even weeks. Thanks so much for putting in your solution I had an extra space in front of my entire http section, and now it works!!! Thank you thank you thank you!!!
Could it be that the config has changed over these past months. I’m a new user and that ssl_certificate property gives me errors when validating the configuration.yaml.