@noysboy wrote:
Im a bit lost on this “err_connection_refused”
I have the fullchain and privkey files in the the /ssl directory and when I restart homeassistant I get:
root@homeassistant:/usr/share/hassio# ha core info arch: amd64 audio_input: null audio_output: null boot: true image: homeassistant/qemux86-64-homeassistant ip_address: 172.30.32.1 last_version: 0.110.4 machine: qemux86-64 port: 8123 ssl: true version: 0.110.3 version_latest: 0.110.4 wait_boot: 600 watchdog: true
However, if I try to connect to anything in chrome I get “err_connection_refused”
Here is my configuration.yaml:
http: ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem homeassistant: internal_url: "http://192.168.0.20:8123" external_url: "https://[xxx].com:4926"
In my router, I have port 4926 -> 8123
Everything works fine, both internally and externally if I comment out the ssl stuff (and change the external to http vs https)
BUT, as soon as I have the ssl stuff in, I lose all access to the web gui and have to go into the command line to edit the yaml and restart.
I can only assume that something in the ssl files is changing some ip/networking info somewhere, but im stuck. Any help is appreciated.
Posts: 2
Participants: 2