Issue accessing front end after restart

Configuration Frontend
1

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.

2

How did you restart?

Have you killed and restarted the container yet?

I seem to have tons of problems with the web interface “restart” button. I can SSH in and check the logs, but it never seems like it actually restarts anything. The service remains ‘active’ and there is no indication that anything is happening. All it seems to do is kill the frontend lol.

I have to usually restart HA via command line (I’m using Home Assistant Core), and even that takes FOREVER to kill. The logs sit there forever waiting for something to be killed that eventually times out. Then it finally stops the HA service and restarts.

Point is, for me, restarting from the web interface only kills the front end and logging into the rpi, if you didn’t know any better, you would assume it was running because the service says ‘active’ and there are no errors in the logs.

I’m also on 103.6.

3

Totally the same problem… Cannot do anything. Only physical server restart solved the problem, but after the next restart problem came again…