Running HAOS on a mini PC, version 17.1. Core and Supervisor 2026.2.3.
Trying to update Core to both 2026.3.0 and 1 never completes. The bar just slowly creeps across as it tries to load and install, then quits. The only way to recover is to do a physical hard reboot, and now my system is becoming extremely unstable. Last month I noticed this happening with updating ESPHome Device Builder, but it would eventually (after 7 times) install. Any ideas as to what is happening? What other info can I provide to help solve this?
Hi
Go to /Setting/System/Logs , there click the 3 dots to the right “RAW-Log” and look for errors, at the time of Update
You can also choose to download the RAW-Log, so you can View it in your fav. txt-editor
Copy relevant section of the errors during Update, and paste them here in a post, Make Sure you Follow the guide HowTo Post code … in the url i gave you in PM
1 Like
Here is the only thing I have seen so far. It is at about 5% loading…
</
File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 117, in resolve
resp = await self._resolver.getaddrinfo(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<5 lines>...
)
^
aiodns.error.DNSError: (12, 'Timeout while contacting DNS servers')
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1562, in _create_direct_connection
hosts = await self._resolve_host(host, port, traces=traces)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1178, in _resolve_host
return await asyncio.shield(resolved_host_task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1209, in _resolve_host_with_throttle
addrs = await self._resolver.resolve(host, port, family=self._family)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp_asyncmdnsresolver/_impl.py", line 140, in resolve
return await super().resolve(host, port, family)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 126, in resolve
raise OSError(None, msg) from exc
OSError: [Errno None] Timeout while contacting DNS servers
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/ring_doorbell/auth.py", line 217, in async_query
resp = await self._session.request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
method, url, headers=headers, data=data, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 779, in _request
resp = await handler(req)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client_middlewares.py", line 36, in single_middleware_handler
return await middleware(req, handler)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 72, in _ssrf_redirect_middleware
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 734, in _connect_and_send_request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
req, traces=traces, timeout=real_timeout
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 672, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1239, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1568, in _create_direct_connection
raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.ring.com:443 ssl:default [Timeout while contacting DNS servers]
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/ring/entity.py", line 65, in _wrap
return await async_func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/>
And to add to this, at 25% there are no more messages, the HAOS instance rebboted itself…
Rob
You have DNS errors, that’s networks errors
So you are right it’s seems to be something “external”
Whether it’s caused by any of your Integrations or add-ons, or your network as a whole, i can’t tell as i don’t know anything about your System, Network, or Add-Ons(Apps)
Does your system works on 2026.2,3 ? and can access internet ?
Can you access Internet, from the minipc ? or windows ?
It works fine with the February core updates, other updates are downloading fine and internet access is working. Network is a home based router going to a Comcast network modem. There are around 60 devices accessing the intranet and around 10 constantly on the inter(extra)net. Everything is IPv4, the DNS are set to Cloudflare. I can try changing them to Google and see what happens.
As i don’t know if above errors are the only ones in your log, and you not show parts with timestamps etc which you have “verified” belongs to the actual start of the executing of Update, or whether.
Only thing in these parts you show point to this
ClientConnectorDNSError: Cannot connect to host api.ring.com:443 ssl:default [Timeout while contacting DNS servers]
AKA ring_doorbell
If above is the only thing “plain-text” you can distinguish , you could try to disable/uninstall this, if it’s anything familiar (however it can also just occur when/because it’s about to shutting down)
Also as you had similar problems month ago while installing ESPHome Device Builder, you could also try to uninstall this again.
PS: I don’t know why you use i.e Cloudflare or Google specific for DNS, Most IP Providers have an auto-dns service, so if you haven’t specific reasons, you shouldn’t have to set anything, just let your ISP handle this
That did it! Changing DNS servers worked…
1 Like
Please Mark You last Post As Solution, the 3 dots to the right of your last Post “Mark Solution”
Great that you got it working again
1 Like