[GH-ISSUE #1990] netbird-coturn-1 not starting. Error installing using self host script #3808

Closed
opened 2026-08-05 00:54:24 -04:00 by saavagebueno · 5 comments
Owner

Originally created by @theglove44 on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1990

Describe the problem

Trying to install netbird using the Self-hosting quickstart guide.

I have an unprivileged Proxmox lxc using Ubuntu Server 22.04.

Ports as stated on the quickstart guide are open in UFW. The lxc is on a dedicated IP address and has a FQD via cloudflare pointed to the server IP.

I'm able to run the single line install script and it goes through the install process. At the starting netbird services stage the pulls complete and 6 of the 7 containers are running. netbird-coturn-1 stays on starting.

I then get an error response from daemon as per the image attached.

Doing a docker ps I can see that netbird-coturn-1 isn't running.
CleanShot 2024-05-15 at 10 17 02

To Reproduce

I have reproduced this behaviour on a number of different proxmox containers.

Expected behavior

The expected behaviour is for the install script to complete and allow me to access my netbird instance via the dashboard FQD

Originally created by @theglove44 on GitHub (May 15, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1990 **Describe the problem** Trying to install netbird using the Self-hosting quickstart guide. I have an unprivileged Proxmox lxc using Ubuntu Server 22.04. Ports as stated on the quickstart guide are open in UFW. The lxc is on a dedicated IP address and has a FQD via cloudflare pointed to the server IP. I'm able to run the single line install script and it goes through the install process. At the starting netbird services stage the pulls complete and 6 of the 7 containers are running. netbird-coturn-1 stays on starting. I then get an error response from daemon as per the image attached. Doing a docker ps I can see that netbird-coturn-1 isn't running. ![CleanShot 2024-05-15 at 10 17 02](https://github.com/netbirdio/netbird/assets/148962746/1293c8c0-c7a8-4d46-aa67-32787d8ac4b6) **To Reproduce** I have reproduced this behaviour on a number of different proxmox containers. **Expected behavior** The expected behaviour is for the install script to complete and allow me to access my netbird instance via the dashboard FQD
saavagebueno added the waiting-feedbacktriage-needed labels 2026-08-05 00:54:24 -04:00
Author
Owner

@mlsmaycon commented on GitHub (May 15, 2024):

can you update the docker-compose.yml and remove the domainname key from the coturn service?

<!-- gh-comment-id:2112441639 --> @mlsmaycon commented on GitHub (May 15, 2024): can you update the docker-compose.yml and remove the domainname key from the coturn service?
Author
Owner

@theglove44 commented on GitHub (May 16, 2024):

updating the compose file was straight forward. It just needs the first line version statement deleted as it's not needed by the latest version of docker. Deleting that solved the version : obsolete message.

I'm not sure how to solve the domainname key issue. I've read through the getting started script to see if I can spot anything but I couldn't see anywhere that might help for that bit.

<!-- gh-comment-id:2114197707 --> @theglove44 commented on GitHub (May 16, 2024): updating the compose file was straight forward. It just needs the first line version statement deleted as it's not needed by the latest version of docker. Deleting that solved the version : obsolete message. I'm not sure how to solve the domainname key issue. I've read through the getting started script to see if I can spot anything but I couldn't see anywhere that might help for that bit.
Author
Owner

@rialco commented on GitHub (Jun 15, 2024):

Ok, so ran into this issue as well, the way I overcome it was following this comment https://github.com/netbirdio/netbird/issues/1990#issuecomment-2112441639. I had to first download the getting-started-with-zitadel script and modify the contents of the script to remove the domainname key as suggested in the comment.

<!-- gh-comment-id:2170713542 --> @rialco commented on GitHub (Jun 15, 2024): Ok, so ran into this issue as well, the way I overcome it was following this comment https://github.com/netbirdio/netbird/issues/1990#issuecomment-2112441639. I had to first download the getting-started-with-zitadel script and modify the contents of the script to remove the domainname key as suggested in the comment.
Author
Owner

@nazarewk commented on GitHub (Apr 23, 2025):

is it still an issue whit the latest NetBird/deployment script versions?

<!-- gh-comment-id:2824736819 --> @nazarewk commented on GitHub (Apr 23, 2025): is it still an issue whit the latest NetBird/deployment script versions?
Author
Owner

@mlsmaycon commented on GitHub (Jun 1, 2025):

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.

<!-- gh-comment-id:2927892640 --> @mlsmaycon commented on GitHub (Jun 1, 2025): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3808