I’m trying since few days now to activate the support of certificates.
I have a signed certificate (not a let’s encrypt one)
I followed that documentation: HTTP - Home Assistant and modified the configuration file like that:
http:
server_port: 8123
ssl_certificate: /etc/mysite.net/homea.mysite.net.crt.pem
ssl_key: /etc/e-nahum.net/homea.mysite.net.key.pem
use_x_forwarded_for: true
trusted_proxies:
- 192.168.1.200 # Add the IP address of the proxy server
- 192.168.1.0/25 # You may also provide the subnet mask
base_url: homea.type.mysite.net:8123
Did you run a command line configuration check (see the common tasks for your install method)?
It’s highly likely if you were to do that, or check the log file, you’d see that it either can’t read the file (no permissions) or the file isn’t there (that path would only be valid if you’re using a Core install method).
Thanks, you are right I can see that the files had been removed and the mysite.net folder is not existing anymore … I did an scp to put the files there and I created the folder by ssh … apparently not the best way… What is the correct way to doing it?
ok I did that … but I probably did something wrong …
When I go to the webinterface, it ask for username / password, second factor and shoot me a message: “Unable to connect to Home Assistant.” | Retry
if I’m using SSH I have a connection refused on TCP 22 …