No longer able to remotely access HASS with HASS/Reverse Proxy Docker containers

Configuration
,
1

Stumped at a recent problem preventing me from accessing a remote instance of Home Assistance.

I’m running HASS 0.69.1 in a Docker instance. That instance sits behind a revere proxy NGNIX Docker container.

That setup worked great the last 2 months but stopped working 5/21. I haven’t made any config changes or added done anything with HASS over the past week so I’m stumped why it suddenly stopped working.

Local instance of HASS works fine (e.g. 192.168.86.xxxx:8123) but the remote version (e.g. xxx.duckdns.org) just spins with the HASS logo.

There are no errors in the home-assistant.log file.

When I look at the container logs and filter for errors, this is all that shows (I’ve googled Key error and didn’t find anything meaningful):

2018-05-23 16:35:52 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/customize.yaml contains duplicate key "binary_sensor.switch_158d0001f400d1". Check lines 134 and 235.


2018-05-23 16:35:52 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "username". Check lines 60 and 62.


2018-05-23 16:35:52 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "password". Check lines 61 and 63.


2018-05-23 16:35:52 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "username". Check lines 62 and 64.


2018-05-23 16:35:52 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "password". Check lines 63 and 65.


2018-05-23 16:35:57 ERROR (SyncWorker_1) [homeassistant.components.light.yeelight] Failed to connect to bulb 192.168.86.183, Desk Light: {'code': -1, 'message': 'client quota exceeded'}


2018-05-23 16:35:59 ERROR (MainThread) [homeassistant.components.sensor] glances: Error on device update!


KeyError: 'total'


2018-05-23 16:35:59 ERROR (MainThread) [homeassistant.components.sensor] glances: Error on device update!


KeyError: 'usage'


2018-05-23 16:44:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/customize.yaml contains duplicate key "binary_sensor.switch_158d0001f400d1". Check lines 134 and 235.


2018-05-23 16:44:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "username". Check lines 60 and 62.


2018-05-23 16:44:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "password". Check lines 61 and 63.


2018-05-23 16:44:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "username". Check lines 62 and 64.


2018-05-23 16:44:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key "password". Check lines 63 and 65.


2018-05-23 16:44:55 ERROR (SyncWorker_19) [homeassistant.components.light.yeelight] Failed to connect to bulb 192.168.86.183, Desk Light: Bulb closed the connection.

config.yaml extract:

http:
  api_password: !secret http_password
  ip_ban_enabled: true
  login_attempts_threshold: 3
2

Key refers to the input data, in this case username.
You may have a misplace quotation marks or comma or maybe same entity entered twice

Go over your config file and look for errors

3

Thank you, I double checked and did find one istance where a username was incorrect. I fixed that and the KeyError is not longer present but I’m still unable to remotely access HASS (e.g. https://xxx.duckdns.org). Local access continues to work fine.

4

If no errors maybe verify port forwarding and domain sending to correct ip

5

That’s the strange part, there haven’t been any changes made to the NGINX reverse proxy or port forwarding rules on the router.

I even wiped everything (including OS) for giggles and re-ran docker-compose file with no luck. I’m stumped and for now, only able to access HASS locally when connected to my home network, which isn’t ideal for my needs.

6

I had some more time to look into this today and don’t think this has anything to do with HASS. Rather, found a few errors in the Let’s Encrypt container which would explain why the local HASS instance works fine.

Once I figure out how to fix it, I’ll post the solution here in case anyone else encounters this in the future.

7

Look at nginx logs

Try external connection and check log for that query and see what fails