Can access HA after 2026.4 update

[sergiobaiao]

The problem

Hello there,

I just ran a docker pull to grab the 2026.4 image but when i started HA i couldn't access the web ui. I use HA container and these are my container logs:

I've reverted to 2026.3 and it works just fine. In 2026.4 despite showing all those message the webui is not available, even though the container listens to the webui port:

ss -ltnp | grep 8123
LISTEN 0 128 0.0.0.0:8123 0.0.0.0:* users:(("python3",pid=756609,fd=11))
LISTEN 0 128 [::]:8123 [::]:* users:(("python3",pid=756609,fd=12))

What version of Home Assistant Core has the issue?

core-2026.4

What was the last working version of Home Assistant Core?

core-2026.3.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

i can't tell

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

hass  | s6-rc: info: service s6rc-oneshot-runner: starting
hass  | s6-rc: info: service s6rc-oneshot-runner successfully started
hass  | s6-rc: info: service fix-attrs: starting
hass  | s6-rc: info: service fix-attrs successfully started
hass  | s6-rc: info: service legacy-cont-init: starting
hass  | s6-rc: info: service legacy-cont-init successfully started
hass  | s6-rc: info: service legacy-services: starting
hass  | services-up: info: copying legacy longrun home-assistant (no readiness notification)
hass  | s6-rc: info: service legacy-services successfully started
hass  | 2026-04-02 11:46:01.206 WARNING (SyncWorker_0) [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
hass  | 2026-04-02 11:46:01.206 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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
hass  | 2026-04-02 11:46:01.207 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mikrotik_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
hass  | 2026-04-02 11:46:01.207 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration llmvision 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
hass  | 2026-04-02 11:46:01.208 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration samsungtv_smart 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
hass  | 2026-04-02 11:46:01.208 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartir 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
hass  | 2026-04-02 11:46:01.208 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
hass  | 2026-04-02 11:46:01.208 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc 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
hass  | 2026-04-02 11:46:01.208 WARNING (SyncWorker_0) [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
hass  | 2026-04-02 11:46:01.209 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration amt8000 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
hass  | 2026-04-02 11:46:01.209 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwains_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
hass  | 2026-04-02 11:46:01.209 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
hass  | 2026-04-02 11:46:01.209 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya_rc 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
hass  | 2026-04-02 11:46:01.209 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered 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
hass  | 2026-04-02 11:46:01.210 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff 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
hass  | 2026-04-02 11:46:01.210 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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
hass  | 2026-04-02 11:46:01.210 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome 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
hass  | 2026-04-02 11:46:01.211 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration whatspie 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
hass  | 2026-04-02 11:46:01.212 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_gateway3 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
hass  | 2026-04-02 11:46:01.212 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration miio_yeelink 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
hass  | 2026-04-02 11:46:01.212 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_miot 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
hass  | 2026-04-02 11:46:01.213 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media 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
hass  | 2026-04-02 11:46:01.213 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration entity_controller 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
hass  | 2026-04-02 11:46:03.889 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.14/site-packages/rich/segment.py:547: SyntaxWarning: 'return' in a 'finally' block
hass  |   return
hass  |
hass  | 2026-04-02 11:46:07.369 ERROR (MainThread) [custom_components.smartir] An error occurred while checking for updates.
hass  | 2026-04-02 11:46:07.373 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'smartir' calls `async_track_state_change` instead of `async_track_state_change_event` which is deprecated and will be removed in Home Assistant 2025.5 at custom_components/smartir/fan.py, line 158: async_track_state_change(self.hass, self._power_sensor,. Please report it to the author of the 'smartir' custom integration
hass  | 2026-04-02 11:46:08.312 ERROR (MainThread) [homeassistant.components.automation] Automation with alias '3-way Sala' failed to setup triggers and has been disabled: Unknown device '29238068d91111b792e6a95b1fd4d66d'
hass  | 2026-04-02 11:46:11.266 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for bt-proxy-eff3d4 @ 192.168.0.29: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.29', port=6053))]: [Errno 113] Connect call failed ('192.168.0.29', 6053) (SocketAPIError)
hass  | 2026-04-02 11:46:11.267 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nscozinha @ 192.168.0.36: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.36', port=6053))]: [Errno 113] Connect call failed ('192.168.0.36', 6053) (SocketAPIError)
hass  | 2026-04-02 11:46:14.423 ERROR (Thread-3) [pylutron] Timeout waiting for GNET prompt, checking if we are back at login
hass  | 2026-04-02 11:46:14.423 ERROR (Thread-3) [pylutron] Fatal error during login
hass  | Traceback (most recent call last):
hass  |   File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
hass  |     return await fut
hass  |            ^^^^^^^^^
hass  |   File "/usr/local/lib/python3.14/site-packages/telnetlib3/stream_reader.py", line 253, in readuntil
hass  |     await self._wait_for_data("readuntil")
hass  |   File "/usr/local/lib/python3.14/site-packages/telnetlib3/stream_reader.py", line 168, in _wait_for_data
hass  |     await self._waiter
hass  | asyncio.exceptions.CancelledError
hass  |
hass  | The above exception was the direct cause of the following exception:
hass  |
hass  | Traceback (most recent call last):
hass  |   File "/usr/local/lib/python3.14/site-packages/pylutron/__init__.py", line 151, in _do_login
hass  |     await asyncio.wait_for(self._reader.readuntil(LutronConnection.PROMPT), timeout=3.0)
hass  |   File "/usr/local/lib/python3.14/asyncio/tasks.py", line 487, in wait_for
hass  |     async with timeouts.timeout(timeout):
hass  |                ~~~~~~~~~~~~~~~~^^^^^^^^^
hass  |   File "/usr/local/lib/python3.14/asyncio/timeouts.py", line 114, in __aexit__
hass  |     raise TimeoutError from exc_val
hass  | TimeoutError
hass  |
hass  | During handling of the above exception, another exception occurred:
hass  |
hass  | Traceback (most recent call last):
hass  |   File "/usr/local/lib/python3.14/site-packages/pylutron/__init__.py", line 183, in _main_loop
hass  |     await self._do_login()
hass  |   File "/usr/local/lib/python3.14/site-packages/pylutron/__init__.py", line 154, in _do_login
hass  |     raise LutronException("Login failed (timeout or invalid credentials)")
hass  | pylutron.LutronException: Login failed (timeout or invalid credentials)

Additional information

No response

[Rolfvgorp]

Had the same problem after upgrade to 2026.4.0 and 2026.4.1. Had to reverse to 2026.3.4 to access web gui again. The only hacs integration we have in common are the spook en webrtc integration. My guess was that the webrtc integration (AlexxIT) from Hacs is the culprit. You dont need it because Ha supports native webrtc. I unistalled webrtc integration form hacs and others i didnt use, after that i did the upgrade to 2026.4.1 again but still no Web GUI, so reversed again to ha core version 2026.3.4

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.