Waiting for zitadel to be ready loop, with quickstart script

[luc-caspar]

Describe the problem

Created a new AWS instance with Ubuntu 24.04.1, 1 CPU and 2Go of memory to test the latest version of Netbird. After installing curl, jq, and docker, I downloaded the getting-started-with-zitadel.sh script. When running said script, it get stuck in a loop waiting for zitadel to be ready, with the following message:

Waiting for Zitadel to become ready  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host ec2-15-152-0-84.ap-northeast-3.compute.amazonaws.com:443 was resolved.
* IPv6: (none)
* IPv4: 172.31.32.216
*   Trying 172.31.32.216:443...
* Connected to ec2-15-152-0-84.ap-northeast-3.compute.amazonaws.com (172.31.32.216) port 443
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
{ [5 bytes data]
* TLSv1.3 (IN), TLS alert, internal error (592):
{ [2 bytes data]
* OpenSSL/3.0.13: error:0A000438:SSL routines::tlsv1 alert internal error
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Closing connection
curl: (35) OpenSSL/3.0.13: error:0A000438:SSL routines::tlsv1 alert internal error

Unable to connect to Zitadel for more than 45s, please check the output above, your firewall rules and the caddy container logs to confirm if there are any issues provisioning TLS certificates

To Reproduce

Go through the self-hosting quickstart guide using ubuntu 22.04 on an AWS instance.

Expected behavior

Access to the management console and all of Netbird's features.

Are you using NetBird Cloud?

No, self-hosted.

NetBird version

latest (0.31.0 at the time of writing).

Screenshots

Additional context

I have already tried the solution provided in issue #1709 to no avail. If relevant, here are the caddy.log