Error connecting to your Home Assistant Server

[naamah75]

Installed extension, configured with server address (I'm sure that the address is correct cause I've tested on browser) and with long live token, then restarted VScode but I get this error:

Error connecting to your Home Assistant Server at https://192.168.1.65:8123, check your network or update your VS Code Settings. Error: 1

VScode:

Versione: 1.32.3 (user setup)
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Data: 2019-03-14T23:43:35.476Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

[maxandersen]

same here - I even notice that it seems to use old values/settings in the error as if settings are not applied when saved.

[keesschollaart81]

I've done a couple of things to get this better.

• The error now does not give a number ('1') but a text (in this case 'ERR_CANNOT_CONNECT')
• The error message now includes a the first couple of characters of the token used
• The settings are from now on by default applied on user-level instead of workspace level (this can still be overridden via the UI or a .vscode/.settings file)
• After updating the settings, the active connection is reset/disconnected and and the new settings will be used. So VS Code does not need a restart any more

Let me know if this is still an issue for you!

[naamah75]

Just updated, now I've the following description:

Error connecting to your Home Assistant Server at https://192.168.1.65:8123 and token 'eyJ0e...', check your network or update your VS Code Settings, make sure to (also) check your workspace settings! Error: ERR_CANNOT_CONNECT

[keesschollaart81]

Are you able to run the demo app from the underlying home-assistant-js-websocket library from the same machine?

[naamah75]

yes, it works! I got a list of all my entities.

[keesschollaart81]

That's good and bad news.. :-) I have no clue! Uninstall / install the extension maybe?

[naamah75]

Already unistalled/reinstalled with no luck... maybe some authorization issue? how I can test it?

[lexitus]

I have what I suspect is the same issue - same symptoms anyway. I've also tried the demo app linked above, with success. I wondered if it might be a certificate problem - since we are both using https.

Running VS Code with --ignore-certificate-errors --verbose still produces the ERR_CANNOT_CONNECT for me - relevant output attached.

[keesschollaart81]

Ah, that's a great catch. Indeed when you try to connect over HTTPS and you have a certificate problem, it does not connect. Now that I have reproduced it, I'll try to find a solution in the coming days. To be continued... Thanks @lexitus!

[naamah75]

I'had the same suspect of @lexitus, but I'm not able to prove. Great job @lexitus and thanks to your support @keesschollaart81

[maxandersen]

just want to confirm that using https://localhost:8123 fails, http://localhost:8123 succeeds. so yeah, something wonky about certificates and/or https as https://localhost:8123 should "just" work :)