A few days ago my Proxmox Server crashed and I had to restart it.
Since that day I can not access the settings dashboard from a fresh openden browser.
I tried 4 different browsers and different computers.
“Error while loading page dashboard.”
On one computer which is running 24/7 and I never closed the browser the settings dashboard still opens. Even after restarting HA and the VM nothing on the other computers, but the 24/7 is still working.
My Android App also still has access to the settings dashboard.
I tried already to clean some Apps which I don’t use and disabling some.
I tried to delete all tokens and logged in new.
I just did a restore from a backup from before the Server crash… no improvement.
Logs don’t show anything suspicious…
[08:23:11] INFO: Home Assistant Core finish process exit code 0
[08:23:11] INFO: Home Assistant Core service shutdown
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-07-09 10:26:00.015 WARNING (SyncWorker_0) [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-07-09 10:26:00.016 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate 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-07-09 10:26:00.017 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration teufel_raumfeld 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-07-09 10:26:00.018 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration remote_homeassistant 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-07-09 10:26:00.019 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration teltonika_extended 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-07-09 10:26:08.817 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esp3201 @ #.#.#.#: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='#.#.#.#', port=6053))]: [Errno 113] Connect call failed ('#.#.#.#', 6053) (SocketAPIError)
2026-07-09 10:26:08.877 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-a @ #.#.#.#: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='#.#.#.#', port=6053))]: [Errno 113] Connect call failed ('#.#.#.#', 6053) (SocketAPIError)```