Failed to download image.. 500.. i/o timeout

Product support
1

Hello,
My Raspberry Pi 3 keeps trying to download images and fails every time even with manual reboots.

Host OS version
balenaOS 2.80.3+rev1

Supervisor version
12.8.8

Logs:
Failed to download image 'registry2.balena-cloud.com/v2/146b2589… ’ due to '(HTTP code 500) server error - Get https://registry2.balena-cloud.com/v2/v2/146b2… : dial tcp: lookup registry2.balena-cloud.com on 127.0.0.2:53: read udp 127.0.0.1:58981->127.0.0.2:53: i/o timeout ’

Will downloading one service at a time solve it? How can this be setup?

Is this a bug with the latest supervisor/OS version?

Thanks
R.

2

Hello,

It seems like it could be a networking problem, I don’t think downloading one service at a time will resolve the issue.

Can you please paste the output of curl -v https://registry2.balena-cloud.com here?

In the mean time, please take a look at this thread as well: NUC cannot download my app

6

Similar issue, I do suspect a networking issue as well, but I’m having trouble pinning it down.

curl -v https://registry2.balena-cloud.com
*   Trying 34.197.149.16:443...
* Connected to registry2.balena-cloud.com (34.197.149.16) port 443 (#0)
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=balena.io
*  start date: May  7 00:00:00 2024 GMT
*  expire date: Jun  4 23:59:59 2025 GMT
*  subjectAltName: host "registry2.balena-cloud.com" matched cert's "*.balena-cloud.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/1.1
> Host: registry2.balena-cloud.com
> User-Agent: curl/7.82.0
> Accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 08 Jan 2025 18:41:54 GMT
< Content-Length: 0
< Connection: keep-alive
< Cache-Control: no-cache
< 
* Connection #0 to host registry2.balena-cloud.com left intact