Issue accessing front end after restart

@diode wrote:

I’m having a heck of a time trying to get my front end to play well after a server restart. I’m running my Home Assistant in docker and recently updated the server that it was running on prior to restarting. Once it was restarted I was unable to connect to the home assistant port via web browser and I was forced to restart the docker.socket and docker.service in order to even access Portainer. Prior to restarting I was unable to stop or even kill a container. I can now see all of the containers running, but now I’m unable to reach the front of either. Prior to restarting the server I made zero changes to the Home Assistant instance which makes me confused on why it didn’t survive the restart. All add-ons are running and are working properly. The docker has no other errors in the logs.

locally using 8123 port or using the Android app. When connecting I receive the following errors:
2020-03-17 04:45:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.XXXXXXXXXXX] Received invalid command: get_panels

2020-03-17 04:45:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.XXXXXXXXXXX] Received invalid command: frontend/get_themes

2020-03-17 04:45:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.XXXXXXXXXXX] Received invalid command: frontend/get_translations

2020-03-17 04:45:31 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.XXXXXXXXXXX] Connection closed by client

I tried accessing the docker to see if there was a way to rebuild the container using the hass command, but that doesn’t appear to be possible.

When trying to access via https using the browser, I receive the following error:

404: Not Found
Any help would be greatly appreciated.
I’m running version 103.6 at the moment.

Posts: 2

Participants: 2

Read full topic