"Home Assistant had trouble connecting to the server" after update to from 0.61 to 0.63.3

Hi,

I recently updated Home Assistant to 0.63.3 in my hassio v1.1 raspberry pi, and while home assistant reports that it’s running over ssh I’m unable to access the admin at :8123.

It spins for a really long time "waiting for 192.168.1.17…then after several minutes I’ll see the error “Home assistant had trouble connecting to the server”.

My console shows some errors

GET http://192.168.1.17:8123/static/mdi-6f045d22d553ce53c94e063400ed68af.html net::ERR_CONNECTION_RESET
(index):1 GET http://192.168.1.17:8123/frontend_latest/frontend-ebcb41952b21503c6a09065b084a638d.html net::ERR_CONNECTION_RESET
(index):1 GET http://192.168.1.17:8123/static/fonts/roboto/Roboto-Medium.ttf net::ERR_CONNECTION_RESET
(index):1 GET http://192.168.1.17:8123/static/fonts/roboto/Roboto-Regular.ttf net::ERR_CONNECTION_RESET
(index):1 GET http://192.168.1.17:8123/frontend_latest/core-aa5473dbea8ac5b75ae0e8239f8e0e38.js net::ERR_CONNECTION_REFUSED
(index):1 Uncaught (in promise) DOMException: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).
(anonymous) @ (index):1

I notice the last one, I’m using http not https, but surely that wouldn’t be causing everything to fail.

Pings to the IP come back in 10ms, so I don’t see why it would be taking so long…

It seems to be running fine from SSH:

core-ssh:~# hassio ha stop
{
    "result": "ok",
    "data": {}
}
core-ssh:~# hassio ha update
{
    "result": "error",
    "message": "Version 0.63.3 is already in use"
}
core-ssh:~# hassio ha start
{
    "result": "ok",
    "data": {}
}

Likewise, nothing out of the ordinary is showing up if I run hassio ha logs, it seems to be managing MQTT et al in the background.

I don’t see any notes about breaking changes in either 0.62 or 0.63…I’m not really sure how to go about debugging this. Can anyone provide any guidance? Thanks!

I believe I had a typo in a configuration file and while I believed the issue was to do with the upgrade it actually wasn’t. Had to reinstall to figure this out. Oh well, all is well I believe.