[GH-ISSUE #1709] Waiting for Zitadel to become ready LOOP #2910

Closed
opened 2026-08-05 00:49:34 -04:00 by saavagebueno · 12 comments
Owner

Originally created by @alfrefarina on GitHub (Mar 15, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1709

Describe the problem

I'm following the Quickstart guide for self hosting, I've successfully opened the required ports and pointed my public domain to the VM.
Unfortunately it gets stuck on Waiting for Zitadel to become ready, I can access the Zitadel page with https://domainname:443/ui/console and I can also see that I get the Lets Encrypt certificate.

If I just type the domain name I get a blank page.

To Reproduce

Follow the Quickstart Guide

Expected behavior

It should go further and show me the NetBird console

Are you using NetBird Cloud?

No

NetBird version

Latest

Screenshots

Screenshot 2024-03-15 at 15 58 41

Originally created by @alfrefarina on GitHub (Mar 15, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1709 **Describe the problem** I'm following the Quickstart guide for self hosting, I've successfully opened the required ports and pointed my public domain to the VM. Unfortunately it gets stuck on Waiting for Zitadel to become ready, I can access the Zitadel page with https://domainname:443/ui/console and I can also see that I get the Lets Encrypt certificate. If I just type the domain name I get a blank page. **To Reproduce** Follow the Quickstart Guide **Expected behavior** It should go further and show me the NetBird console **Are you using NetBird Cloud?** No **NetBird version** Latest **Screenshots** ![Screenshot 2024-03-15 at 15 58 41](https://github.com/netbirdio/netbird/assets/42649788/7eb330ea-2a45-468e-bea9-d7bcfd71cda9)
saavagebueno added the waiting-feedbackzitadelself-hostinggetting-started labels 2026-08-05 00:49:35 -04:00
Author
Owner

@braginini commented on GitHub (Mar 15, 2024):

hey @alfrefarina
Are you running behind Cloudflare?
Also, could you please send the output of docker compose logs command?

<!-- gh-comment-id:1999886276 --> @braginini commented on GitHub (Mar 15, 2024): hey @alfrefarina Are you running behind Cloudflare? Also, could you please send the output of `docker compose logs` command?
Author
Owner

@alfrefarina commented on GitHub (Mar 15, 2024):

Hello,
thanks for answering, no I'm not running behind Cloudflare.
These are the logs, I hope I sent them correctly.
netbird_docker_logs.txt

<!-- gh-comment-id:1999894402 --> @alfrefarina commented on GitHub (Mar 15, 2024): Hello, thanks for answering, no I'm not running behind Cloudflare. These are the logs, I hope I sent them correctly. [netbird_docker_logs.txt](https://github.com/netbirdio/netbird/files/14617402/netbird_docker_logs.txt)
Author
Owner

@mlsmaycon commented on GitHub (Mar 17, 2024):

@alfrefarina, can you confirm if the issue persists and if you are running with the required VM size?

The database used by Zitadel is quite resource-intensive, so you should have at least 1CPU and 2GB of memory

<!-- gh-comment-id:2002560567 --> @mlsmaycon commented on GitHub (Mar 17, 2024): @alfrefarina, can you confirm if the issue persists and if you are running with the required VM size? The database used by Zitadel is quite resource-intensive, so you should have at least 1CPU and 2GB of memory
Author
Owner

@alfrefarina commented on GitHub (Mar 17, 2024):

Yes, the issue still persists. My machine is an Ubuntu 20.04 with 4CPU and 4GB of memory.

<!-- gh-comment-id:2002587192 --> @alfrefarina commented on GitHub (Mar 17, 2024): Yes, the issue still persists. My machine is an Ubuntu 20.04 with 4CPU and 4GB of memory.
Author
Owner

@mlsmaycon commented on GitHub (Mar 17, 2024):

the script validates the zitadel endpoint by issuing a request to Zitadel using the domain and generated PAT.

you can test it out with the following command:

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"

Is possible that the system can't access the docker container using this domain

<!-- gh-comment-id:2002590551 --> @mlsmaycon commented on GitHub (Mar 17, 2024): the script validates the zitadel endpoint by issuing a request to Zitadel using the domain and generated PAT. you can test it out with the following command: ```shell 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" ``` Is possible that the system can't access the docker container using this domain
Author
Owner

@alfrefarina commented on GitHub (Mar 17, 2024):

If I run these commands the script gets stuck "Trying IP:443.." at 0%, if I access the URL https://$NETBIRD_DOMAIN/auth/v1/users/me it says: "code: 16, message: auth header missing"

<!-- gh-comment-id:2002592465 --> @alfrefarina commented on GitHub (Mar 17, 2024): If I run these commands the script gets stuck "Trying IP:443.." at 0%, if I access the URL https://$NETBIRD_DOMAIN/auth/v1/users/me it says: "code: 16, message: auth header missing"
Author
Owner

@mlsmaycon commented on GitHub (Mar 17, 2024):

can you update your /etc/hosts file and add the NETBIRD_DOMAIN value pointing to a local VM IP address and then try again?

<!-- gh-comment-id:2002595309 --> @mlsmaycon commented on GitHub (Mar 17, 2024): can you update your /etc/hosts file and add the NETBIRD_DOMAIN value pointing to a local VM IP address and then try again?
Author
Owner

@alfrefarina commented on GitHub (Mar 17, 2024):

If I point the NETBIRD_DOMAIN to the local IP address your commands seem to work, but shouldn't the domain point to the Public IP?

<!-- gh-comment-id:2002597071 --> @alfrefarina commented on GitHub (Mar 17, 2024): If I point the NETBIRD_DOMAIN to the local IP address your commands seem to work, but shouldn't the domain point to the Public IP?
Author
Owner

@mlsmaycon commented on GitHub (Mar 17, 2024):

only for remote clients, the services don't need to use private IP addresses, so changing the /etc/hosts should be fine.

<!-- gh-comment-id:2002597930 --> @mlsmaycon commented on GitHub (Mar 17, 2024): only for remote clients, the services don't need to use private IP addresses, so changing the /etc/hosts should be fine.
Author
Owner

@alfrefarina commented on GitHub (Mar 17, 2024):

Sorry but I'm confused, if I rerun the quickstart script with NETBIRD_DOMAIN pointing to my local private IP address I won't get a certificate, because it needs my Public IP address, or am I wrong?

<!-- gh-comment-id:2002598455 --> @alfrefarina commented on GitHub (Mar 17, 2024): Sorry but I'm confused, if I rerun the quickstart script with NETBIRD_DOMAIN pointing to my local private IP address I won't get a certificate, because it needs my Public IP address, or am I wrong?
Author
Owner

@mlsmaycon commented on GitHub (Mar 17, 2024):

This will only happen if you update the domain in your DNS provider. However, updating the local server's /etc/hosts file should not affect certificate provisioning.

<!-- gh-comment-id:2002600361 --> @mlsmaycon commented on GitHub (Mar 17, 2024): This will only happen if you update the domain in your DNS provider. However, updating the local server's /etc/hosts file should not affect certificate provisioning.
Author
Owner

@alfrefarina commented on GitHub (Mar 17, 2024):

Ok, thank you very much, I rerun the script and I can successfully reach NetBird's dashboard.

<!-- gh-comment-id:2002600899 --> @alfrefarina commented on GitHub (Mar 17, 2024): Ok, thank you very much, I rerun the script and I can successfully reach NetBird's dashboard.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2910