When I use the script for installation, it keeps stalling at "Waiting for Zitadel to become ready...".
When I use the script for installation, it keeps stalling at "Waiting for Zitadel to become ready...".
After I saw this topic #1709 , I used the code
PAT=$(cat ./machinekey/zitadel-admin-sa.token)
NETBIRD_DOMAIN=<your_instance_domain>
curl -v --fail -o /dev/null "https://$NETBIRD_DOMAIN/auth/v1/users/me" -H "Authorization: Bearer $PAT"
and the result I got is as follows:
* Establish HTTP proxy tunnel to *****.org:443
> CONNECT ******.org:443 HTTP/1.1
> Host: ******.org:443
> User-Agent: curl/7.81.0
> Proxy-Connection: Keep-Alive
< HTTP/1.1 200 OK
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.0 (OUT), TLS header, Unknown (21):
} [5 bytes data]
* TLSv1.3 (OUT), TLS alert, decode error (562):
} [2 bytes data]
* error:0A000126:SSL routines::unexpected eof while reading
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
* Closing connection 0
curl: (35) error:0A000126:SSL routines::unexpected eof while reading
@firekirin67 are you able to solve the issue, i have the same issue, i am stuck with Zitadel to become ready LOOP, what to do
@firekirin67你能解决这个问题吗?我遇到了同样的问题,我被困在 Zitadel 中,无法进入准备循环,该怎么办
I have already resolved it. You can check issue #1709 to see if the outcome can be helpful.
Hello @firekirin67,
We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.
Could you please confirm if the issue is still there?
We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.
Thanks for your contribution to improving the project!
closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.