Hello everyone, I have recently been trying out OpenBalena. My setup consists of two x86 machines: Balena Server and the CLI are on the same machine, while Balena OS runs on the other. I am using a self-signed certificate and a self-hosted DNS server. However, I encountered an issue at the final step of the tutorial: I am unable to push to the registry.
any response would be helpful, thank you!
epiloguess:~/balena$ balena deploy --noparent-check myApp --debug
[debug] new argv=[/home/epiloguess/playground/balena-cli/balena,/snapshot/balena-cli/bin/run.js,deploy,--noparent-check,myApp] length=5
[debug] Deprecation check: 0.71320 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[Debug] Parsing input...
[Debug] Loading project...
[Debug] Resolving project...
[Info] No "docker-compose.yml" file found at "/home/epiloguess/balena"
[Info] Creating default composition with source: "/home/epiloguess/balena"
[Debug] Creating project...
[debug] Event tracking error: Timeout awaiting 'response' for 0ms
[Info] Everything is up to date (use --build to force a rebuild)
[Info] Creating release...
[Debug] Tagging images...
[Debug] Authorizing push...
[Info] Pushing images to registry...
Retrying "registry2.epiloguess.com/v2/1b4e11cccd419889021ab159c9046c6d:latest" after 2.0s (1 of 2) due to: Error: Get "https://registry2.epiloguess.com/v2/": EOF
Retrying "registry2.epiloguess.com/v2/1b4e11cccd419889021ab159c9046c6d:latest" after 2.8s (2 of 2) due to: Error: Get "https://registry2.epiloguess.com/v2/": EOF
[Debug] Saving image registry2.epiloguess.com/v2/1b4e11cccd419889021ab159c9046c6d
[Debug] Untagging images...
[Info] Saving release...
[Error] Deploy failed
Get "https://registry2.epiloguess.com/v2/": EOF
epiloguess:~/balena$ balena device list
ID UUID DEVICE NAME DEVICE TYPE FLEET STATUS IS ONLINE SUPERVISOR VERSION OS VERSION DASHBOARD URL
1 4ddfb88 wide-potato generic-amd64 admin/myapp Idle true 16.6.1 balenaOS 6.0.24+rev1 https://dashboard.epiloguess.com/devices/4ddfb88c6ce8fcf0a3efc4fd01e1ac01/summary
epiloguess:~/balena$ curl -v https://registry2.epiloguess.com/v2
* Host registry2.epiloguess.com:443 was resolved.
* IPv6: (none)
* IPv4: 192.168.1.219
* Trying 192.168.1.219:443...
* Connected to registry2.epiloguess.com (192.168.1.219) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=Washington; L=Seattle; O=balena; OU=openBalena; CN=epiloguess.com
* start date: Dec 16 09:33:00 2024 GMT
* expire date: Jan 17 09:33:00 2026 GMT
* subjectAltName: host "registry2.epiloguess.com" matched cert's "*.epiloguess.com"
* issuer: C=US; ST=Washington; L=Seattle; O=balena; OU=openBalena; CN=balena Server CA 0
* SSL certificate verify ok.
* Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256
* Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://registry2.epiloguess.com/v2
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: registry2.epiloguess.com]
* [HTTP/2] [1] [:path: /v2]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET /v2 HTTP/2
> Host: registry2.epiloguess.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 301
< content-type: text/html; charset=utf-8
< docker-distribution-api-version: registry/2.0
< location: /v2/
< date: Tue, 17 Dec 2024 03:10:48 GMT
< content-length: 39
<
<a href="/v2/">Moved Permanently</a>.
* Connection #0 to host registry2.epiloguess.com left intact