[GH-ISSUE #244] using the Self-hosting Guide without success #566

Closed
opened 2026-08-05 00:39:09 -04:00 by saavagebueno · 9 comments
Owner

Originally created by @chmis8000 on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/244

1:management.json:
management json

2:docker-compose.yml:
2022-02-27_214029

3:Coturn_log.txt

4:https://github.com/wiretrustee/wiretrustee/blob/main/docs/self-hosting.md
vs
README.md start with ""Running Dashboard, Management, Signal and Coturn"
The descriptions are inconsistent.

In addition to modifying setup.env, what else do I need to modify?
Can the documentation be improved? Thank you.

Originally created by @chmis8000 on GitHub (Feb 27, 2022). Original GitHub issue: https://github.com/netbirdio/netbird/issues/244 1:management.json: ![management json](https://user-images.githubusercontent.com/19686229/155884822-6d684879-462a-40fe-aa23-3bbb3d906c41.png) 2:docker-compose.yml: ![2022-02-27_214029](https://user-images.githubusercontent.com/19686229/155884766-dd0d7b1e-dcea-46e5-bda3-de73af10c07d.png) 3:[Coturn_log.txt](https://github.com/wiretrustee/wiretrustee/files/8148437/Coturn_log.txt) 4:https://github.com/wiretrustee/wiretrustee/blob/main/docs/self-hosting.md vs [README.md](https://github.com/wiretrustee/wiretrustee#readme) start with ""Running Dashboard, Management, Signal and Coturn" The descriptions are inconsistent. In addition to modifying setup.env, what else do I need to modify? Can the documentation be improved? Thank you.
Author
Owner

@Neptunespace commented on GitHub (Feb 27, 2022):

Same here

<!-- gh-comment-id:1053693823 --> @Neptunespace commented on GitHub (Feb 27, 2022): Same here
Author
Owner

@mlsmaycon commented on GitHub (Feb 27, 2022):

Hello @chmis8000 @Neptunespace, sorry to hear that you are facing issues. I will review the guide and update it according to the latest changes.

<!-- gh-comment-id:1053705529 --> @mlsmaycon commented on GitHub (Feb 27, 2022): Hello @chmis8000 @Neptunespace, sorry to hear that you are facing issues. I will review the guide and update it according to the latest changes.
Author
Owner

@mlsmaycon commented on GitHub (Mar 5, 2022):

Hello @chmis8000 and @Neptunespace,

We've updated the documentation and templates to reflect the latest changes and to offer a better support for turn configuration as well.

<!-- gh-comment-id:1059737604 --> @mlsmaycon commented on GitHub (Mar 5, 2022): Hello @chmis8000 and @Neptunespace, We've updated the documentation and templates to reflect the latest changes and to offer a better support for turn configuration as well.
Author
Owner

@chmis8000 commented on GitHub (Mar 13, 2022):

@mlsmaycon it's not ok.
Today,change from centos8 system to ubuntu20.4 system/centos7.6.
signal,management,dashboard no error,coturn has many errors.
a
b
c
full log: error.txt

<!-- gh-comment-id:1066105316 --> @chmis8000 commented on GitHub (Mar 13, 2022): @mlsmaycon it's not ok. Today,change from centos8 system to ubuntu20.4 system/centos7.6. signal,management,dashboard no error,coturn has many errors. ![a](https://user-images.githubusercontent.com/19686229/158062291-8617794e-00a5-48fd-ac9d-dcc3314555c4.png) ![b](https://user-images.githubusercontent.com/19686229/158062338-2adff076-2318-46e5-a16b-2a0091f63b2c.png) ![c](https://user-images.githubusercontent.com/19686229/158062347-5b5e36eb-aac6-4f3a-baae-cc5589c9464f.png) full log: [error.txt](https://github.com/wiretrustee/wiretrustee/files/8239776/error.txt)
Author
Owner

@mlsmaycon commented on GitHub (Mar 14, 2022):

hello @chmis8000 most of the errors and warnings from Coturn are caused by default configuration settings. These are ok to ignore as they don't affect Coturn's functionality.

The only settings that can be improved from our end are the certificate files path, that we can comment them out or point to the same files used by dashboard and management. Let me evaluate if they will work as expected or if we need further changes for that.

<!-- gh-comment-id:1066489010 --> @mlsmaycon commented on GitHub (Mar 14, 2022): hello @chmis8000 most of the errors and warnings from Coturn are caused by default configuration settings. These are ok to ignore as they don't affect Coturn's functionality. The only settings that can be improved from our end are the certificate files path, that we can comment them out or point to the same files used by dashboard and management. Let me evaluate if they will work as expected or if we need further changes for that.
Author
Owner

@chmis8000 commented on GitHub (Mar 15, 2022):

Do these errors of coturn not affect the use?
Is it the cause of auth0.com misconfiguration, now the error is:
Oops... Service not found: https://xxx.pcapp.cc
dashboard

<!-- gh-comment-id:1068666904 --> @chmis8000 commented on GitHub (Mar 15, 2022): Do these errors of coturn not affect the use? Is it the cause of auth0.com misconfiguration, now the error is: Oops... Service not found: https://xxx.pcapp.cc ![dashboard](https://user-images.githubusercontent.com/19686229/158504488-5e9efe58-3183-4c0a-ae72-a57059a33cd8.png)
Author
Owner

@chmis8000 commented on GitHub (Mar 17, 2022):

@mlsmaycon
The "Oops... Service not found" problem has been solved
The reason is that the URL written by WIRETRUSTEE_AUTH0_AUDIENCE did not add / at the end.
I suggest you strengthen the documentation or improve the automatic judgment of the program.

But,However, the client cannot connect, the record in client.log file is:
time="2022-03-17T13:44:42+08:00" level=error msg="failed to connect to service CLI interface context deadline exceeded".
Please take a look, what might be the problem?

<!-- gh-comment-id:1070351485 --> @chmis8000 commented on GitHub (Mar 17, 2022): @mlsmaycon The "Oops... Service not found" problem has been solved The reason is that the URL written by WIRETRUSTEE_AUTH0_AUDIENCE did not add / at the end. I suggest you strengthen the documentation or improve the automatic judgment of the program. But,However, the client cannot connect, the record in client.log file is: time="2022-03-17T13:44:42+08:00" level=error msg="failed to connect to service CLI interface context deadline exceeded". Please take a look, what might be the problem?
Author
Owner

@chmis8000 commented on GitHub (Mar 18, 2022):

I know the reason, I will open another post

<!-- gh-comment-id:1072071747 --> @chmis8000 commented on GitHub (Mar 18, 2022): I know the reason, I will open another post
Author
Owner

@brandonros commented on GitHub (Apr 26, 2022):

What is the reason?

<!-- gh-comment-id:1110114025 --> @brandonros commented on GitHub (Apr 26, 2022): What is the reason?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#566