Updates stopped to work on RPI - DNS problem?

Hi,

I’m getting the following when trying to update supervisor or addons:

20-09-06 19:37:49 ERROR (SyncWorker_7) [supervisor.docker.interface] Can’t install homeassistant/armv7-hassio-supervisor:240 -> 500 Server Error: Internal Server Error (“Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.5.1:53: read udp 192.168.5.10:43866->192.168.5.1:53: i/o timeout”).
20-09-06 19:37:49 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor fails!

20-09-06 19:55:24 INFO (SyncWorker_4) [supervisor.docker.interface] Update image homeassistant/armv7-addon-ssh:8.6.0 to homeassistant/armv7-addon-ssh:8.7.0
20-09-06 19:55:24 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/armv7-addon-ssh tag 8.7.0.
20-09-06 19:55:34 ERROR (SyncWorker_4) [supervisor.docker.interface] Can’t install homeassistant/armv7-addon-ssh:8.7.0 -> 500 Server Error: Internal Server Error (“Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.5.1:53: read udp 192.168.5.10:39773->192.168.5.1:53: i/o timeout”).

It trying to run traceroute to “registry-1.docker.io” from hassio terminal addon - it works OK.

What can it be?

I was having the same issue as, I suspected it is a DNS resolution issue. Restart your router and also try and ping it from the console to confirm you can resolve to the address

1 Like

Same for me.
When I had misconfigured DNS I had the same issue.

*edit: literally confirms what @jssting and I have mentioned:

lookup registry-1.docker.io ... ->192.168.5.1:53: i/o timeout”).

53 is the port for DNS, and your host 192.168.5.10 failed for perform a DNS query on host 192.168.5.1 (which is probably your router, I guess.)

Also, please format code logs with code blocks.

Hey Guys,

Yes, I was trying to reboot router, supervisor and the whole Pi. Same results. And even as I wrote - traceroute to the same site works from terminal/ssh plugin. Any thoughts?

Can you log into the base device via SSH and confirm if the traceroute/ping works from there as well… I had resolution from within Hassio, but not from the underlying Linux, once I had resolution working from there, it worked fine. I suspect it is using Curl from the underlying OS to do the query. I may be wrong, but that’s what fixed it for me.

I’m using a pure hassio installation on RPI4. I don’t think there is “underlying linux” or any other system. And I’m using a “Terminal & SSH add-on” to get a command line.

I have the same issue but only for Homeassistant core, HAS and supervisor are updated without issue.
I am also on a RPI.