Core: Self-signed certificates don't work in HASS.io

[NodeGuy]

Home Assistant release (hass --version):
0.57.0

Python release (python3 --version):

core-ssh:/config# python3 --version
-ash: python3: not found

Component/platform:
platform

Description of problem:
I followed the instructions to secure the web interface with a self-signed certificate on a fresh install. After restarting Home Assistant the web page fails to load on either port 8123 or 443.

Expected:

Expect the web page to load, secured via SSL.

Problem-relevant configuration.yaml entries and steps to reproduce:

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: example.duckdns.org:8123

  ssl_certificate: /ssl/certificate.pem
  ssl_key: /ssl/privkey.pem

1. openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out certificate.pem
2. Update configuration.yaml as above.
3. hassio homeassistant restart

[ryanm101]

Is this still an issue?

Is there a reason for you not to use letsencrypt instead of self-signed?

[ccarrizosa]

Hi,

I cannot use Let's Encrypt as my Hass instance is not accessible outside my local network.

I guess the instruccions are not valid for hassio installations because when you connect via ssh you're connecting to the docker container and openssl is not installed here. This is why @NodeGuy get the -ash: python3: not found error.

[ccarrizosa]

Hi again,

I've developed a simple hassio addon to create self-signed certificates. You'll find it at my hass.io addons repository.

If you find it useful I can do a pull request to hassio-addons repository.

Regards,

[NodeGuy]

Thank you! Can you confirm that these do or don't work with the iOS app?

[ccarrizosa]

Ups! I'm sorry because I haven't any device with iOS, then I cannot confirm you. But, I use chrome to access to hass and it works: I can access home assistant via HTTPS using the self-signed certificate generated with the addon. The only point is Chrome displays a warning when you access home-assistant using a self-signed certificate because it doesn't come from any CA.

[MacGulliver]

Same Problem here, would love to use my own Certificates issued from my CA.
HA 0.6
ResinOS 1.1
configuration.yaml as above
tried a few different certs as of now but dosnt seem to have to do with the used cert.

[NodeGuy]

@ccarrizosa OK, thanks for letting me know. If I have some free time in the future I'll try your add-on with the iOS app. Thanks for your contribution!

@MacGulliver Did you try @ccarrizosa's add-on?

[MacGulliver]

@NodeGuy not yet, on the List for the Weekend (i hope) ;D

cheers

[xander2]

@NodeGuy and @MacGulliver

If you want to go the manual route, I just configured my fresh install of hass.io with following entries in the configuration.yaml:

http:
  ssl_certificate: certificate.pem
  ssl_key: privkey.pem

and I copied both files into the /config folder via the ssh add-on, as this location is accessible from all docker containers. Both files need to be created on a computer with openssl installed.
This works and I can access my instance at https://hassio.local:8123.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[MacGulliver]

Sorry for the late reply, been busy lately. I've transitioned from HASSIO on a RPi to a more powerful Solution on a FreeNAS Box. For that Reason i didn't investigate this Cert Issue further on my End.

Thanks anyway

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍