Can't get into the frontend after moving Docker container to a new host

@NMe84 wrote:

I upgraded my NAS and as such moved all my Docker containers over from the old one to the new one. I had no issues whatsoever with Mosquitto and Zigbee2MQTT but I can’t for the life of me seem to get Home Assistant itself running anymore.

Symptoms:

• The Docker container is running and keeps running. Doesn’t crash.
• When I go to the UI in a browser that previously visited it through the old server or with the Android app, it either keeps trying to load for a few minutes followed by “Unable to connect to Home Assistant.” and the retry button, or it shows that screen right away.
• When I go to the UI in a browser that has not previously used it, I get a login screen. When I log in with my actual credentials I get the same error as above, and if I purposefully use bad credentials I get directed back to the login screen to try again, so something seems to be running.
• None of my automations work, so nothing much else seems to be running.

This is my log file:

2020-06-04 01:44:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for zigbee2mqtt_networkmap which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:47 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for discord_game which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:54 ERROR (SyncWorker_6) [homeassistant.components.octoprint] Endpoint: printer Failed to update OctoPrint status. Error: 409 Client Error: CONFLICT for url: http://octopi-cr-x:80/api/printer
2020-06-04 01:44:56 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2020-06-04 01:44:56 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2020-06-04 02:03:40 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from ***.***.***.***

Funnily enough that last line only gets added when I use the correct credentials, actual bad login attempts don’t get logged.

I should probably add that I’m using a reverse proxy for SSL termination, this is my config for that:

http:
  server_host: 127.0.0.1
  use_x_forwarded_for: true
  trusted_proxies: 127.0.0.1
#  base_url: https://sub.domain.tld

I tried it both with and without the base_url option but the result is the same.

In case it helps, this shows my Docker setup:

CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS                 PORTS                                                                                                        NAMES
1805ea6bc601        homeassistant/home-assistant:latest   "/init"                  About an hour ago   Up 40 minutes                                                                                                                       HomeAssistant
8daf0012a85b        koenkk/zigbee2mqtt                    "./run.sh"               3 hours ago         Up 3 hours                                                                                                                          Zigbee2MQTT
264e74fdd0c3        eclipse-mosquitto:latest              "/docker-entrypoint.…"   3 hours ago         Up 3 hours             0.0.0.0:1883->1883/tcp, 0.0.0.0:9001->9001/tcp                                                               Mosquitto

Home Assistant and Zigbee2MQTT both were started with --net=host, which is why the ports section is empty.

Does anyone know what I can do to get past this?

Posts: 1

Participants: 1

Read full topic