I have created my own certificate authority using Zentyal:
I have the following files:
CA-key-and-cert.zip:
ca-cert.crt
ca-public-key.pem
(Ugh… Typo due to frustration…)
keys-and-certs-homeassistant.zip:
homeassistant-cert.crt
homeassistant.p12 (PKCS12)
homeassistant-private-key.pem
homeassistant-public-key.pem
Since Home Assistant expects a .pem file for both certificate and key, what should I do to get it to work for Home Assistant? I’ve converted a variety of files (except .pem) to .pem files to no available and tried different combinations of it although either one of the ssl_key or ssl_certificate field should have a CA file.
Not that I plan to expose Home Assistant over the Internet with strong password and SSL, but I will be using VPN in the future. However, I do like to try and get HTTPS with Home Assistant to work.
And can’t Home Assistant just read either or both a .crt and .p12 file? It would make my life much easier than being so inflexible that I use .pem files no matter what I do.
I did, but I don’t know how I configure Home Assistant with certificates. According to my configuration, it seems to me Home Assistant expects the extension to end in .pem for both certificates and private key and it worked since I have my own CA certificate installed in my desktop and my smartphone. The .crt file may have to be renamed to .pem in order for Home Assistant to work.
Thanks, that’s what I ended up doing. Everything is working great now. Not the same as when I used the defacto standard here of DuckDNS. That had all kinds of issues and problems with connecting and getting the phones working, and when I would connect to the web interface remotely the login would always fail. With a righteous certificate all those issues went away.