Closed tsvi closed 4 years ago
172.16.0.0/24
does not include 172.30.32.2
... So the source IP is not visible...
🤦♂️ changed it to 172.16.0.0/12 (the private ip range), but still failing.
Well, the real source IP should now be revealed...? (as in the actual client that the proxy, proxies for).
It looks according to the timing of the error that it is the supervisor that's trying to access it (error 1 I mentioned in the issue). How is the supervisor supposed to access home assisstant? Is it supposed to have a token that maybe is missing/was deleted? Or maybe I'm supposed to whitelist its IP?
With the latest release of the supervisor, I managed to discover the culprit as the log now had the following message as well:
20-05-10 05:25:55 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for my_user
Took me a few minutes, as MQTT seemed to work fine and my camera which I hooked up via MQTT was passing the data fine. Until o figured it was the zigbee2mqtt add-on I installed, started but never configured.
Once I setup username and password for the core_mosquitto broker, all is fine now.
Thanks,
Tsvi
Thank you, this was exactly my problem! I had installed zigbee2mqtt and hadn't set it up yet but it seems I had chosen start at reboot and had rebooted. Thank you!
Home Assistant release with the issue:
Operating environment (HassOS/Generic):
Supervisor logs:
Description of problem:
20-05-03 09:23:39 ERROR (MainThread) [supervisor.auth] Can't request auth on Home Assistant!
Login attempt or request with invalid authentication from 172.30.32.2 (that's the reverse proxy
I have a reverse proxy setup with Nginx Proxy Manager and have the following in my config: