-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Home Assistant Supervisor failed to configure #99795
Comments
have the same problem since today without update Home Assistant 2023.9.0. |
Also running latest Home assistant 2023.9.0 with supervisor 2023.8.3 First error in log with no further details: Failed to to call /ingress/session - 'NoneType' object is not iterable followed by: Logger: homeassistant.config_entries Error setting up entry Supervisor for hassio Next error: Logger: homeassistant.helpers.entity Failed to set state, fall back to unknown |
Hi, Same issue after updating to 2023.9 Logger: homeassistant.config_entries Error setting up entry Supervisor for hassio |
Same problem. |
Restarting whole VM Proxmox did not work for me |
I just installed fresh Homeassistant OS for first time ever. Got this same error out of the box |
Also noted here home-assistant/supervisor#4531 as a supervisor issue. |
Update: It is back after another reboot. |
System completely dead. Could not recover. Even reverting to 2023.8.4 did not help... |
Finally salvaged my system by doing a docker kill homeassistant, then docker rmi (image ID of assistant), allowing me enough time to do a ha core stop, then ha core update --version 2023.8.3. Then, rebooting host, got a whole bunch of error messages in ha core logs, but at least the system is back up and running... Whew. |
indeed, reboot doesnt help, and its not related to 2023.9.0, i see the same on 2023.8.4
|
Hello guys, I did a lot of analysis and find out: From my location github.com response with 2 IP: 140.82.121.4 and 140.82.121.3, and from my home network I can't ping 140.82.121.3. So when I reboot HA and at that time my network pointing github.com to IP adress 140.82.121.4 HA starting fine. But if my network at this time pointing github.com to IP 140.82.121.3 HA supervisor do not start up because supervisor can't access github.com. Here it's traceroutes: Tracing route to lb-140-82-121-4-fra.github.com [140.82.121.4] 1 3 ms 3 ms 9 ms unifi.localdomain [192.168.8.1] Trace complete. C:\Users\marnau>tracert 140.82.121.3 Tracing route to lb-140-82-121-3-fra.github.com [140.82.121.3] 1 2 ms 2 ms 2 ms unifi.localdomain [192.168.8.1] Trace complete. So I think problem not HA update or internet provider, but problem is that github server with IP 140.82.121.3 drop packet from some IP ranges. |
Home Assistant 2023.8.4 i try to update with command line and get error masage. Make a cold reboot and update from cammand Line 2nd time now it works. Home Assistant 2023.9.0 But i have the error. after several resart i can fix it for the moment with a cold start |
People have had luck with fixing their problem by changing their DNS address in HA, see comments here #99862 I myself had my pihole DNS with the issue and now it's fixed. Settings > System > Network > IPv4 > change DNS to 1.1.1.1 or 8.8.8.8 |
same here since update 2023.9.1 |
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hassio documentation |
This is also an issue for me. Core 2023.11.2 Sometimes HA starts well and others this problem arises. Using adguard home as DNS. Tried to force DNS in HA to 1.1.1.1 It seems to workaround the issue but I dont know if always or only sometimes. But this is not a solution for me as I need my local DNS names. Adguard DNS name resolution is working fine except for this. |
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. |
The problem
Logger: homeassistant.config_entries
Source: components/hassio/handler.py:540
First occurred: 06:41:15 (1 occurrences)
Last logged: 06:41:15
Error setting up entry for hassio
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/init.py", line 665, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 257, in async_config_entry_first_refresh
await self._async_refresh(
File "/usr/src/homeassistant/homeassistant/components/hassio/init.py", line 974, in _async_refresh
await self.hassio.refresh_updates()
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 37, in _wrapper
data = await funct(*argv, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 540, in send_command
request = await self.websession.request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 560, in _request
await resp.start(conn)
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 899, in start
message, payload = await protocol.read() # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
asyncio.exceptions.CancelledError: Global task timeout
What version of Home Assistant Core has the issue?
Home Assistant 2023.9.0
What was the last working version of Home Assistant Core?
Home Assistant 2023.8.0
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Home Assistant Supervisor
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: