SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-15 12:42:22 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

docker-compose not working #63

New Issue
Closed
opened 2025-11-20 05:05:35 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:05:35 -05:00
Owner
Copy Link

Originally created by @yangchuansheng on GitHub (Sep 7, 2021).

just clone the repo and run docker-compose but the management container is not in healthy state，here is docker logs:

$ nerdctl ps -a
1d3b485a839e    docker.io/wiretrustee/dashboard:main                  "/usr/bin/supervisor…"    10 minutes ago    Up                           0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp    infrastructure_files_dashboard_1
20c21f7116ab    docker.io/coturn/coturn:latest                        "docker-entrypoint.s…"    10 minutes ago    Up                                                                       infrastructure_files_coturn_1
8e15df6d5a42    docker.io/wiretrustee/management:0.1.0-rc-1           "/go/bin/wiretrustee…"    10 minutes ago    Exited (1) 10 minutes ago    0.0.0.0:33073->33073/tcp                    infrastructure_files_management_1
ceb443b5623e    docker.io/wiretrustee/signal:latest                   "/go/bin/wiretrustee…"    10 minutes ago    Up                           0.0.0.0:10000->10000/tcp                    infrastructure_files_signal_1

$ nerdctl logs infrastructure_files_management_1
time="2021-09-07T05:33:41Z" level=info msg="started server: localhost:33073"
time="2021-09-07T05:33:41Z" level=fatal msg="failed to serve http server: Get \"\": unsupported protocol scheme \"\""

here is config.json

{
    "Stuns": [
        {
            "Proto": "udp",
            "URI": "stun:stun.wiretrustee.com:3468",
            "Username": "",
            "Password": null
        }
    ],
    "TURNConfig": {
        "Turns": [
            {
                "Proto": "udp",
                "URI": "turn:stun.wiretrustee.com:3468",
                "Username": "some_user",
                "Password": "c29tZV9wYXNzd29yZA=="
            }
        ],
        "CredentialsTTL": "1h",
        "Secret": "c29tZV9wYXNzd29yZA==",
        "TimeBasedCredentials": true
    },
    "Signal": {
        "Proto": "http",
        "URI": "signal.wiretrustee.com:10000",
        "Username": "",
        "Password": null
    },
    "Datadir": "",
    "HttpConfig": {
        "LetsEncryptDomain": "",
        "Address": "0.0.0.0:3000",
        "AuthDomain": "",
        "AuthClientId": "",
        "AuthClientSecret": "",
        "AuthCallback": "http://localhost:3000/callback"
    }
}

any suggestions ??

Originally created by @yangchuansheng on GitHub (Sep 7, 2021). just clone the repo and run docker-compose but the management container is not in healthy state，here is docker logs: ```bash $ nerdctl ps -a 1d3b485a839e docker.io/wiretrustee/dashboard:main "/usr/bin/supervisor…" 10 minutes ago Up 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp infrastructure_files_dashboard_1 20c21f7116ab docker.io/coturn/coturn:latest "docker-entrypoint.s…" 10 minutes ago Up infrastructure_files_coturn_1 8e15df6d5a42 docker.io/wiretrustee/management:0.1.0-rc-1 "/go/bin/wiretrustee…" 10 minutes ago Exited (1) 10 minutes ago 0.0.0.0:33073->33073/tcp infrastructure_files_management_1 ceb443b5623e docker.io/wiretrustee/signal:latest "/go/bin/wiretrustee…" 10 minutes ago Up 0.0.0.0:10000->10000/tcp infrastructure_files_signal_1 $ nerdctl logs infrastructure_files_management_1 time="2021-09-07T05:33:41Z" level=info msg="started server: localhost:33073" time="2021-09-07T05:33:41Z" level=fatal msg="failed to serve http server: Get \"\": unsupported protocol scheme \"\"" ``` here is config.json ```json { "Stuns": [ { "Proto": "udp", "URI": "stun:stun.wiretrustee.com:3468", "Username": "", "Password": null } ], "TURNConfig": { "Turns": [ { "Proto": "udp", "URI": "turn:stun.wiretrustee.com:3468", "Username": "some_user", "Password": "c29tZV9wYXNzd29yZA==" } ], "CredentialsTTL": "1h", "Secret": "c29tZV9wYXNzd29yZA==", "TimeBasedCredentials": true }, "Signal": { "Proto": "http", "URI": "signal.wiretrustee.com:10000", "Username": "", "Password": null }, "Datadir": "", "HttpConfig": { "LetsEncryptDomain": "", "Address": "0.0.0.0:3000", "AuthDomain": "", "AuthClientId": "", "AuthClientSecret": "", "AuthCallback": "http://localhost:3000/callback" } } ``` any suggestions ??
saavagebueno commented 2025-11-20 05:05:36 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Sep 8, 2021):

hey @yangchuansheng
Indeed, there was a bug in the compose file.
We have released a new version and you could try again:
https://github.com/wiretrustee/wiretrustee/releases/tag/v0.1.0-rc.2

The important part is that you will need to register Auth0 account for the system to function properly.
This is due to the fact that we haven't implemented our own user management system but used Auth0 service instead.
We are also preparing the documentation website to describe all the steps.

P.S. If you would like to just try the system without setting up anything, you could go ahead with https://beta.wiretrustee.com/

Let me know if this helps!

@braginini commented on GitHub (Sep 8, 2021): hey @yangchuansheng Indeed, there was a bug in the compose file. We have released a new version and you could try again: https://github.com/wiretrustee/wiretrustee/releases/tag/v0.1.0-rc.2 The important part is that you will need to register [Auth0](https://auth0.com/) account for the system to function properly. This is due to the fact that we haven't implemented our own user management system but used Auth0 service instead. We are also preparing the documentation website to describe all the steps. P.S. If you would like to just try the system without setting up anything, you could go ahead with [https://beta.wiretrustee.com/](https://beta.wiretrustee.com/) Let me know if this helps!
saavagebueno commented 2025-11-20 05:05:36 -05:00
Author
Owner
Copy Link

@yangchuansheng commented on GitHub (Sep 12, 2021):

hey @yangchuansheng
Indeed, there was a bug in the compose file.
We have released a new version and you could try again:
v0.1.0-rc.2 (release)

The important part is that you will need to register Auth0 account for the system to function properly.
This is due to the fact that we haven't implemented our own user management system but used Auth0 service instead.
We are also preparing the documentation website to describe all the steps.

P.S. If you would like to just try the system without setting up anything, you could go ahead with beta.wiretrustee.com

Let me know if this helps!

Still confused, what is the value of AuthKeysLocation and AuthIssuer? I cannot find them in auth0.com

@yangchuansheng commented on GitHub (Sep 12, 2021): > hey @yangchuansheng > Indeed, there was a bug in the compose file. > We have released a new version and you could try again: > [`v0.1.0-rc.2` (release)](https://github.com/wiretrustee/wiretrustee/releases/tag/v0.1.0-rc.2) > > The important part is that you will need to register [Auth0](https://auth0.com/) account for the system to function properly. > This is due to the fact that we haven't implemented our own user management system but used Auth0 service instead. > We are also preparing the documentation website to describe all the steps. > > P.S. If you would like to just try the system without setting up anything, you could go ahead with [beta.wiretrustee.com](https://beta.wiretrustee.com/) > > Let me know if this helps! Still confused, what is the value of AuthKeysLocation and AuthIssuer? I cannot find them in auth0.com
saavagebueno commented 2025-11-20 05:05:36 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Sep 13, 2021):

Hi @yangchuansheng
There are 2 key cases that we use Auth0 for:

  1. Registration and Login to the Dashboard
  2. Protecting Management API from an unauthorized access.

Dashboard is a single page React web application and it sends JWT with every request to the Management API. Management has to validate those tokens and public key and issuer are used there.

Check the flow description here.
https://auth0.com/docs/microsites/protect-api/protect-api#how-it-works

So where to get these properties?
Here is the Auth0 Go backend guide
https://auth0.com/docs/quickstart/backend/golang

We understand the need for the clear documentation and getting started guide. We are working on that!

@braginini commented on GitHub (Sep 13, 2021): Hi @yangchuansheng There are 2 key cases that we use Auth0 for: 1. Registration and Login to the Dashboard 2. Protecting Management API from an unauthorized access. Dashboard is a single page React web application and it sends JWT with every request to the Management API. Management has to validate those tokens and public key and issuer are used there. Check the flow description here. https://auth0.com/docs/microsites/protect-api/protect-api#how-it-works So where to get these properties? Here is the Auth0 Go backend guide https://auth0.com/docs/quickstart/backend/golang We understand the need for the clear documentation and getting started guide. We are working on that!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#63
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?