Greetings. I am running Home Assistant on a VM within Proxmox.
Installation method: Home Assistant OS
Core: 2026.9.0
Supervisor: 2026.08.0
Operating System: 18.2
Frontend: 20260826.4
Everything appears to be working, I’ve not run across any unexpected failures. However, every 15 seconds, this is recorded to my logs:
Logger: homeassistant.components.http.forwarded
Source: components/http/forwarded.py:126
Integration: HTTP (documentation, issues)
First occurred: 10:56:28 AM (1632 occurrences)
Last logged: 5:44:17 PM
Invalid IP address in X-Forwarded-For:
I am using Godoxy as my reverse proxy and it works as expected. I can completely shut down Godoxy and connect to Home Assistant via IP address and every 15 seconds the error continues to log, so that rules out the issue being my proxy.
I use Nabu Casa cloud, but only enable connections from the outside world when I am out of home zone and my firewall has no path from the internet to Home Assistant.
Looking at similar topics, people typically get a value at the end of the “X-Forwarded-For” message, which would help to find the problem but I do not, it’s just empty. I’ve run a netstat -a over and over trying to see if something is connecting that could produce this error and with the proxy server off, the only thing connected to port 8123 is my local workstation.
I’ve been able to rule some items out, but am at a bit of a loss how to narrow down and identify the source of the problem and was hoping for some suggestions. How might I see the full text of the header that is causing this error?
What determines what one person considers a problem vs another? It’s the characters that we rolled in life. My mind says if I can get the error to stop without spending too much time, that’s the path forward. If it is too time consuming to resolve that’s usually when my OCD-like thoughts surrender and I can ignore it.
I also like everything clean, but I don’t* look at the logs, and when I do, I look at other problems.
But okay, let’s solve it somehow sometime…
*I do, almost every day, but not at the raw ones where I see…
Are you sure you aren't scared of logs? If not, open this expandable!
2026-09-05 00:27:14.857 WARNING (SyncWorker_0) [annotatedyaml.constructors] YAML file /config/configuration.yaml contains duplicate key "panel_custom". Check lines 14 and 29
2026-09-05 00:27:14.860 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration eink_dashboard 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
2026-09-05 00:27:14.862 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration bubble_card_tools 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
2026-09-05 00:27:14.864 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration spook_inverse 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
2026-09-05 00:27:14.865 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration tapo_rv30 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
2026-09-05 00:27:14.866 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration tplink_router 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
2026-09-05 00:27:14.867 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration browser_mod 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
2026-09-05 00:27:14.871 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration spook 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
2026-09-05 00:27:14.873 WARNING (SyncWorker_1) \[homeassistant.loader\] We found a custom integration 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
2026-09-05 00:27:24.781 WARNING (MainThread) \[custom_components.eink_dashboard\] Calendar entity 'calendar.janik' is not in the states snapshot; events will not be fetched and the widget will render blank. Check that the entity exists in Home Assistant.
2026-09-05 00:27:26.365 ERROR (MainThread) \[homeassistant.components.esphome.manager\] Unexpected device found at 192.168.1.109; expected \`jadiv-presense-v1-pracovna\` with mac address \`ac:27:6e:7f:2a:c4\`, found \`jadiv-fridgecam-v1\` with mac address \`c8:85:41:2a:0f:04\`
2026-09-05 00:27:27.314 WARNING (MainThread) \[aioesphomeapi.reconnect_logic\] Can't connect to ESPHome API for jclock240001 @ 192.168.1.106: Error connecting to \[AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.106', port=6053))\]: \[Errno 113\] Connect call failed ('192.168.1.106', 6053) (SocketAPIError)
2026-09-05 00:29:50.939 WARNING (MainThread) \[aioesphomeapi.reconnect_logic\] Can't connect to ESPHome API for jclock430002 @ 192.168.1.110: Error connecting to \[AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.110', port=6053))\]: \[Errno 113\] Connect call failed ('192.168.1.110', 6053) (SocketAPIError)
2026-09-05 00:42:32.514 WARNING (SyncWorker_4) \[annotatedyaml.constructors\] YAML file /config/configuration.yaml contains duplicate key "panel_custom". Check lines 14 and 29
2026-09-05 01:16:19.780 WARNING (SyncWorker_2) \[annotatedyaml.constructors\] YAML file /config/configuration.yaml contains duplicate key "panel_custom". Check lines 14 and 29