SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-28 08:52:37 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Quickstart Guide is not working as intended #698

New Issue
Closed
opened 2025-11-20 05:16:09 -05:00 by saavagebueno · 12 comments
saavagebueno commented 2025-11-20 05:16:09 -05:00
Owner
Copy Link

Originally created by @Jadefalkner on GitHub (Mar 13, 2024).

I tried to install netbird selfhosted with the short quickstart guide. It installed all the docker container, but when i log in the first time into the gui with the admin user, you have the same view than with a normal unpriviledged user. I cant connect any peers and there i am stuck

To Reproduce

Just follow the Quickstart Guide

Expected behavior

Normal Function

Are you using NetBird Cloud?

No

NetBird version

3.4

Additional context

The output of "docker-compose logs management":

management_1 | 2024-03-13T21:43:22Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration
management_1 | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.url.tld/.well-known/openid-configuration Get "https://netbird.url.tld/.well-known/openid-configuration": dial tcp xxx.xxx.xxx.xxx: i/o timeout
management_1 | 2024-03-13T21:43:53Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration
management_1 | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.url.tld/.well-known/openid-configuration Get "https://netbird.url.tld/.well-known/openid-configuration": dial tcp xxx.xxx.xxx.xxx:443: i/o timeout
management_1 | 2024-03-13T21:44:24Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration

Originally created by @Jadefalkner on GitHub (Mar 13, 2024). I tried to install netbird selfhosted with the short quickstart guide. It installed all the docker container, but when i log in the first time into the gui with the admin user, you have the same view than with a normal unpriviledged user. I cant connect any peers and there i am stuck **To Reproduce** Just follow the Quickstart Guide **Expected behavior** Normal Function **Are you using NetBird Cloud?** No **NetBird version** 3.4 **Additional context** The output of "docker-compose logs management": management_1 | 2024-03-13T21:43:22Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration management_1 | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.url.tld/.well-known/openid-configuration Get "https://netbird.url.tld/.well-known/openid-configuration": dial tcp xxx.xxx.xxx.xxx: i/o timeout management_1 | 2024-03-13T21:43:53Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration management_1 | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.url.tld/.well-known/openid-configuration Get "https://netbird.url.tld/.well-known/openid-configuration": dial tcp xxx.xxx.xxx.xxx:443: i/o timeout management_1 | 2024-03-13T21:44:24Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration
saavagebueno added the triage-needed label 2025-11-20 05:16:09 -05:00
saavagebueno commented 2025-11-20 05:16:10 -05:00
Author
Owner
Copy Link

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

Hello @Jadefalkner it seems like your management system is not resolving the domain correctly.

Can you add the extra hosts configuration in the docker-compose.yml for the management service with either the public VM address or one of the local addresses of the docker host?

@mlsmaycon commented on GitHub (Mar 13, 2024): Hello @Jadefalkner it seems like your management system is not resolving the domain correctly. Can you add the extra hosts configuration in the docker-compose.yml for the management service with either the public VM address or one of the local addresses of the docker host?
saavagebueno commented 2025-11-20 05:16:10 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 13, 2024):

He can resolve the right IP, in my copy above "netbird.url.tld" resolves to the right "xxx.xxx.xxx.xxx". One strange thing i noticed is, that, when i start the env up, it kills my portainer agent (cant connect anymore) it seems to me that something strange with the network is happening.

@Jadefalkner commented on GitHub (Mar 13, 2024): He can resolve the right IP, in my copy above "netbird.url.tld" resolves to the right "xxx.xxx.xxx.xxx". One strange thing i noticed is, that, when i start the env up, it kills my portainer agent (cant connect anymore) it seems to me that something strange with the network is happening.
saavagebueno commented 2025-11-20 05:16:10 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 14, 2024):

alright, i dug a little deeper, from my machine i can get the file:

jadefalkner@newmachine:~/netbird$ curl https://netbird.url.tld/.well-known/openid-configuration
{"issuer":"https://netbird.url.tld","authorization_endpoint":"https://netbird.url.tld/oauth/v2/authorize","token_endpoint":"https://netbird.url.tld/oauth/v2/token","introspection_endpoint":"https://netbird.url.tld/oauth/v2/introspect","userinfo_endpoint":"https://netbird.url.tld/oidc/v1/userinfo","revocation_endpoint":"https://netbird.url.tld/oauth/v2/revoke","end_session_endpoint":"https://netbird.url.tld/oidc/v1/end_session","device_authorization_endpoint":"https://netbird.url.tld/oauth/v2/device_authorization","jwks_uri":"https://netbird.url.tld/oauth/v2/keys","scopes_supported":["openid","profile","email","phone","address","offline_access"],"response_types_supported":["code","id_token","id_token token"],"grant_types_supported":["authorization_code","implicit","refresh_token","client_credentials","urn:ietf:params:oauth:grant-type:jwt-bearer","urn:ietf:params:oauth:grant-type:device_code"],"subject_types_supported":["public"],"id_token_signing_alg_values_supported":["RS256"],"request_object_signing_alg_values_supported":["RS256"],"token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post","private_key_jwt"],"token_endpoint_auth_signing_alg_values_supported":["RS256"],"revocation_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post","private_key_jwt"],"revocation_endpoint_auth_signing_alg_values_supported":["RS256"],"introspection_endpoint_auth_methods_supported":["client_secret_basic","private_key_jwt"],"introspection_endpoint_auth_signing_alg_values_supported":["RS256"],"claims_supported":["sub","aud","exp","iat","iss","auth_time","nonce","acr","amr","c_hash","at_hash","act","scopes","client_id","azp","preferred_username","name","family_name","given_name","locale","email","email_verified","phone_number","phone_number_verified"],"code_challenge_methods_supported":["S256"],"ui_locales_supported":["bg","de","en","es","fr","it","ja","mk","pl","pt","zh"],"request_parameter_supported":true,"request_uri_parameter_supported":false}

from the container i get the mentioned timeout. so it seems that there is the problem, but i cant see what it is, it was a fresh machine with a fresh installation

here is part of the docker network inspect netbird_netbird

[
    {
        "Name": "netbird_netbird",
        "Id": "c3e09868ac5323d9186d48ead8089ceab35966f65528c6e515ca492bb86a0289",
        "Created": "2024-03-14T08:55:21.044237239+01:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.23.0.0/16",
                    "Gateway": "172.23.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": true,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "33d5399db5344f383a9800eea29139b2633da11810293d495f57b80ed08fde2a": {
                "Name": "netbird_management_1",
                "EndpointID": "f1c6489db3c0a67d8990b7c9724017d960e410c9d8ff3029b419b66e664c5815",
                "MacAddress": "02:42:ac:17:00:07",
                "IPv4Address": "172.23.0.7/16",
                "IPv6Address": ""
            },
            "90a1fb095b2acda9e9578c41ebf7d3af3e7194d0ba8f1027479f4de6de028768": {
                "Name": "netbird_signal_1",
                "EndpointID": "cc3e89bb52f5ec44033691def5c19d68d9e110a51a6a5af9c4d43043af2032c1",
                "MacAddress": "02:42:ac:17:00:06",
                "IPv4Address": "172.23.0.6/16",
                "IPv6Address": ""
            },
            "bc392f2672a5cd71efb68d8d355d6f3b69ba497112382492989bb0e79d0a38bd": {
                "Name": "netbird_zitadel_1",
                "EndpointID": "675af90fe8b230513640c5f242e09c02d705f3db91f1453ff32642e3b00cb0da",
                "MacAddress": "02:42:ac:17:00:04",
                "IPv4Address": "172.23.0.4/16",
                "IPv6Address": ""
@Jadefalkner commented on GitHub (Mar 14, 2024): alright, i dug a little deeper, from my machine i can get the file: ``` jadefalkner@newmachine:~/netbird$ curl https://netbird.url.tld/.well-known/openid-configuration {"issuer":"https://netbird.url.tld","authorization_endpoint":"https://netbird.url.tld/oauth/v2/authorize","token_endpoint":"https://netbird.url.tld/oauth/v2/token","introspection_endpoint":"https://netbird.url.tld/oauth/v2/introspect","userinfo_endpoint":"https://netbird.url.tld/oidc/v1/userinfo","revocation_endpoint":"https://netbird.url.tld/oauth/v2/revoke","end_session_endpoint":"https://netbird.url.tld/oidc/v1/end_session","device_authorization_endpoint":"https://netbird.url.tld/oauth/v2/device_authorization","jwks_uri":"https://netbird.url.tld/oauth/v2/keys","scopes_supported":["openid","profile","email","phone","address","offline_access"],"response_types_supported":["code","id_token","id_token token"],"grant_types_supported":["authorization_code","implicit","refresh_token","client_credentials","urn:ietf:params:oauth:grant-type:jwt-bearer","urn:ietf:params:oauth:grant-type:device_code"],"subject_types_supported":["public"],"id_token_signing_alg_values_supported":["RS256"],"request_object_signing_alg_values_supported":["RS256"],"token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post","private_key_jwt"],"token_endpoint_auth_signing_alg_values_supported":["RS256"],"revocation_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post","private_key_jwt"],"revocation_endpoint_auth_signing_alg_values_supported":["RS256"],"introspection_endpoint_auth_methods_supported":["client_secret_basic","private_key_jwt"],"introspection_endpoint_auth_signing_alg_values_supported":["RS256"],"claims_supported":["sub","aud","exp","iat","iss","auth_time","nonce","acr","amr","c_hash","at_hash","act","scopes","client_id","azp","preferred_username","name","family_name","given_name","locale","email","email_verified","phone_number","phone_number_verified"],"code_challenge_methods_supported":["S256"],"ui_locales_supported":["bg","de","en","es","fr","it","ja","mk","pl","pt","zh"],"request_parameter_supported":true,"request_uri_parameter_supported":false} ``` from the container i get the mentioned timeout. so it seems that there is the problem, but i cant see what it is, it was a fresh machine with a fresh installation here is part of the docker network inspect netbird_netbird ``` [ { "Name": "netbird_netbird", "Id": "c3e09868ac5323d9186d48ead8089ceab35966f65528c6e515ca492bb86a0289", "Created": "2024-03-14T08:55:21.044237239+01:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.23.0.0/16", "Gateway": "172.23.0.1" } ] }, "Internal": false, "Attachable": true, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "33d5399db5344f383a9800eea29139b2633da11810293d495f57b80ed08fde2a": { "Name": "netbird_management_1", "EndpointID": "f1c6489db3c0a67d8990b7c9724017d960e410c9d8ff3029b419b66e664c5815", "MacAddress": "02:42:ac:17:00:07", "IPv4Address": "172.23.0.7/16", "IPv6Address": "" }, "90a1fb095b2acda9e9578c41ebf7d3af3e7194d0ba8f1027479f4de6de028768": { "Name": "netbird_signal_1", "EndpointID": "cc3e89bb52f5ec44033691def5c19d68d9e110a51a6a5af9c4d43043af2032c1", "MacAddress": "02:42:ac:17:00:06", "IPv4Address": "172.23.0.6/16", "IPv6Address": "" }, "bc392f2672a5cd71efb68d8d355d6f3b69ba497112382492989bb0e79d0a38bd": { "Name": "netbird_zitadel_1", "EndpointID": "675af90fe8b230513640c5f242e09c02d705f3db91f1453ff32642e3b00cb0da", "MacAddress": "02:42:ac:17:00:04", "IPv4Address": "172.23.0.4/16", "IPv6Address": "" ```
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

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

can you try adding the following tot he management service configuration in the docker compose?

extra_hosts:
 - "netbird.url.tld:172.23.0.1"

then run: docker compose up -d

And test again.

@mlsmaycon commented on GitHub (Mar 14, 2024): can you try adding the following tot he management service configuration in the docker compose? ```yaml extra_hosts: - "netbird.url.tld:172.23.0.1" ``` then run: `docker compose up -d` And test again.
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 14, 2024):

okay, i installed it again, so the network changed to 172.20.0.1/16
i put the following into the docker.compose.yml

    command: [
      "--port", "80",
      "--log-file", "console",
      "--log-level", "info",
      "--disable-anonymous-metrics=false",
      "--single-account-mode-domain=netbird.selfhosted",
      "--dns-domain=netbird.selfhosted",
      "--idp-sign-key-refresh-enabled",
    extra_hosts:
      - "netbird.url.tld:172.20.0.1"

and got the following message after docker-compose up -d:

netbird_coturn_1 is up-to-date
netbird_caddy_1 is up-to-date
netbird_dashboard_1 is up-to-date
Recreating netbird_management_1 ... 
netbird_signal_1 is up-to-date
netbird_crdb_1 is up-to-date
Recreating netbird_management_1 ... done

the management node still provides the error message but here with the wrong IP i think

management_1  | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.odensjakt.de/.well-known/openid-configuration Get "https://netbird.odensjakt.de/.well-known/openid-configuration": dial tcp 172.20.0.1:443: i/o timeout
management_1  | 2024-03-14T14:49:14Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration

because now it tries to get the file from 172.20.0.1

And service docker status tells me that the file should be on 172.20.0.3

CGroup: /system.slice/docker.service
             ├─30449 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --ip=213.199.45.99
             ├─36975 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8080 -container-ip 172.20.0.3 -container-port 8080
             ├─36984 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8080 -container-ip 172.20.0.3 -container-port 8080
             ├─37004 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.20.0.3 -container-port 443
             ├─37012 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 443 -container-ip 172.20.0.3 -container-port 443
             ├─37033 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80 -container-ip 172.20.0.3 -container-port 80
             └─37040 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 80 -container-ip 172.20.0.3 -container-port 80
@Jadefalkner commented on GitHub (Mar 14, 2024): okay, i installed it again, so the network changed to 172.20.0.1/16 i put the following into the docker.compose.yml ``` command: [ "--port", "80", "--log-file", "console", "--log-level", "info", "--disable-anonymous-metrics=false", "--single-account-mode-domain=netbird.selfhosted", "--dns-domain=netbird.selfhosted", "--idp-sign-key-refresh-enabled", extra_hosts: - "netbird.url.tld:172.20.0.1" ``` and got the following message after docker-compose up -d: ``` netbird_coturn_1 is up-to-date netbird_caddy_1 is up-to-date netbird_dashboard_1 is up-to-date Recreating netbird_management_1 ... netbird_signal_1 is up-to-date netbird_crdb_1 is up-to-date Recreating netbird_management_1 ... done ``` the management node still provides the error message but here with the wrong IP i think ``` management_1 | Error: failed reading provided config file: /etc/netbird/management.json: failed fetching OIDC configuration from endpoint https://netbird.odensjakt.de/.well-known/openid-configuration Get "https://netbird.odensjakt.de/.well-known/openid-configuration": dial tcp 172.20.0.1:443: i/o timeout management_1 | 2024-03-14T14:49:14Z INFO management/cmd/management.go:449: loading OIDC configuration from the provided IDP configuration endpoint https://netbird.url.tld/.well-known/openid-configuration ``` because now it tries to get the file from 172.20.0.1 And service docker status tells me that the file should be on 172.20.0.3 ``` CGroup: /system.slice/docker.service ├─30449 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --ip=213.199.45.99 ├─36975 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8080 -container-ip 172.20.0.3 -container-port 8080 ├─36984 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8080 -container-ip 172.20.0.3 -container-port 8080 ├─37004 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.20.0.3 -container-port 443 ├─37012 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 443 -container-ip 172.20.0.3 -container-port 443 ├─37033 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80 -container-ip 172.20.0.3 -container-port 80 └─37040 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 80 -container-ip 172.20.0.3 -container-port 80 ```
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

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

can you change the address to the server VM address?

@mlsmaycon commented on GitHub (Mar 14, 2024): can you change the address to the server VM address?
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 14, 2024):

Alright, changing the extra_hosts to 172.20.0.3 seems to do the trick

management_1  | 2024-03-14T14:53:26Z INFO management/cmd/management.go:486: overriding PKCEAuthorizationFlow.TokenEndpoint with a new value: https://netbird.url.tld/oauth/v2/token, previously configured value: 
management_1  | 2024-03-14T14:53:26Z INFO management/cmd/management.go:489: overriding PKCEAuthorizationFlow.AuthorizationEndpoint with a new value: https://netbird.url.tld/oauth/v2/authorize, previously configured value: 
management_1  | 2024-03-14T14:53:26Z INFO management/server/telemetry/app_metrics.go:177: enabled application metrics and exposing on http://0.0.0.0:8081
management_1  | 2024-03-14T14:53:26Z INFO management/server/store.go:92: using SQLite store engine
management_1  | 2024-03-14T14:53:27Z INFO management/cmd/management.go:160: update config with activity store key
@Jadefalkner commented on GitHub (Mar 14, 2024): Alright, changing the extra_hosts to 172.20.0.3 seems to do the trick ``` management_1 | 2024-03-14T14:53:26Z INFO management/cmd/management.go:486: overriding PKCEAuthorizationFlow.TokenEndpoint with a new value: https://netbird.url.tld/oauth/v2/token, previously configured value: management_1 | 2024-03-14T14:53:26Z INFO management/cmd/management.go:489: overriding PKCEAuthorizationFlow.AuthorizationEndpoint with a new value: https://netbird.url.tld/oauth/v2/authorize, previously configured value: management_1 | 2024-03-14T14:53:26Z INFO management/server/telemetry/app_metrics.go:177: enabled application metrics and exposing on http://0.0.0.0:8081 management_1 | 2024-03-14T14:53:26Z INFO management/server/store.go:92: using SQLite store engine management_1 | 2024-03-14T14:53:27Z INFO management/cmd/management.go:160: update config with activity store key ```
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

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

As you might run docker compose down in the future, is better not to rely on the docker IP address, so the address from the main interface in the host is a better option.

@mlsmaycon commented on GitHub (Mar 14, 2024): As you might run docker compose down in the future, is better not to rely on the docker IP address, so the address from the main interface in the host is a better option.
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 14, 2024):

what puzzles me more:

tcp        0      0 xxx.xxx.xxx.xxx:3478      0.0.0.0:*               LISTEN      65534      202731     42837/turnserver    
tcp        0      0 xxx.xxx.xxx.xxx:3478      0.0.0.0:*               LISTEN      65534      202817     42837/turnserver    
tcp        0      0 xxx.xxx.xxx.xxx:3478      0.0.0.0:*               LISTEN      65534      202811     42837/turnserver    
tcp        0      0 xxx.xxx.xxx.xxx:3478      0.0.0.0:*               LISTEN      65534      202725     42837/turnserver    
tcp        0      0 172.21.0.1:3478         0.0.0.0:*               LISTEN      65534      202733     42837/turnserver    
tcp        0      0 172.21.0.1:3478         0.0.0.0:*               LISTEN      65534      202819     42837/turnserver    
tcp        0      0 172.21.0.1:3478         0.0.0.0:*               LISTEN      65534      202813     42837/turnserver    
tcp        0      0 172.21.0.1:3478         0.0.0.0:*               LISTEN      65534      202727     42837/turnserver    
tcp        0      0 127.0.0.1:3478          0.0.0.0:*               LISTEN      65534      202730     42837/turnserver    
tcp        0      0 127.0.0.1:3478          0.0.0.0:*               LISTEN      65534      202816     42837/turnserver    
tcp        0      0 127.0.0.1:3478          0.0.0.0:*               LISTEN      65534      202810     42837/turnserver    
tcp        0      0 127.0.0.1:3478          0.0.0.0:*               LISTEN      65534      202724     42837/turnserver    
tcp        0      0 172.17.0.1:3478         0.0.0.0:*               LISTEN      65534      202732     42837/turnserver    
tcp        0      0 172.17.0.1:3478         0.0.0.0:*               LISTEN      65534      202818     42837/turnserver    
tcp        0      0 172.17.0.1:3478         0.0.0.0:*               LISTEN      65534      202812     42837/turnserver    
tcp        0      0 172.17.0.1:3478         0.0.0.0:*               LISTEN      65534      202726     42837/turnserver

is this normal behaviour?

@Jadefalkner commented on GitHub (Mar 14, 2024): what puzzles me more: ``` tcp 0 0 xxx.xxx.xxx.xxx:3478 0.0.0.0:* LISTEN 65534 202731 42837/turnserver tcp 0 0 xxx.xxx.xxx.xxx:3478 0.0.0.0:* LISTEN 65534 202817 42837/turnserver tcp 0 0 xxx.xxx.xxx.xxx:3478 0.0.0.0:* LISTEN 65534 202811 42837/turnserver tcp 0 0 xxx.xxx.xxx.xxx:3478 0.0.0.0:* LISTEN 65534 202725 42837/turnserver tcp 0 0 172.21.0.1:3478 0.0.0.0:* LISTEN 65534 202733 42837/turnserver tcp 0 0 172.21.0.1:3478 0.0.0.0:* LISTEN 65534 202819 42837/turnserver tcp 0 0 172.21.0.1:3478 0.0.0.0:* LISTEN 65534 202813 42837/turnserver tcp 0 0 172.21.0.1:3478 0.0.0.0:* LISTEN 65534 202727 42837/turnserver tcp 0 0 127.0.0.1:3478 0.0.0.0:* LISTEN 65534 202730 42837/turnserver tcp 0 0 127.0.0.1:3478 0.0.0.0:* LISTEN 65534 202816 42837/turnserver tcp 0 0 127.0.0.1:3478 0.0.0.0:* LISTEN 65534 202810 42837/turnserver tcp 0 0 127.0.0.1:3478 0.0.0.0:* LISTEN 65534 202724 42837/turnserver tcp 0 0 172.17.0.1:3478 0.0.0.0:* LISTEN 65534 202732 42837/turnserver tcp 0 0 172.17.0.1:3478 0.0.0.0:* LISTEN 65534 202818 42837/turnserver tcp 0 0 172.17.0.1:3478 0.0.0.0:* LISTEN 65534 202812 42837/turnserver tcp 0 0 172.17.0.1:3478 0.0.0.0:* LISTEN 65534 202726 42837/turnserver ``` is this normal behaviour?
saavagebueno commented 2025-11-20 05:16:11 -05:00
Author
Owner
Copy Link

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

Yes, you can update the turnserver.conf and adjust some parameters. Use this example file: https://github.com/netbirdio/netbird/blob/main/infrastructure_files/turnserver.conf.tmpl#L60

Ensure you keep the external-ip as it is helpful to always use the public IP on turn responses.

@mlsmaycon commented on GitHub (Mar 14, 2024): Yes, you can update the turnserver.conf and adjust some parameters. Use this example file: https://github.com/netbirdio/netbird/blob/main/infrastructure_files/turnserver.conf.tmpl#L60 Ensure you keep the external-ip as it is helpful to always use the public IP on turn responses.
saavagebueno commented 2025-11-20 05:16:12 -05:00
Author
Owner
Copy Link

@Jadefalkner commented on GitHub (Mar 14, 2024):

Thank you.

I might have a clue what happened. My iptables accept all traffic to 443 only from eth0. This could be the problem, but i have to check that later

Regards,

Ronny

@Jadefalkner commented on GitHub (Mar 14, 2024): Thank you. I might have a clue what happened. My iptables accept all traffic to 443 only from eth0. This could be the problem, but i have to check that later Regards, Ronny
saavagebueno commented 2025-11-20 05:16:12 -05:00
Author
Owner
Copy Link

@seanzamora commented on GitHub (Aug 25, 2024):

I resolved this issue by setting extra_hosts domain to point to Hosts serve private IP for example: 192.168.0.116.

` extra_hosts:

  • "netbird.example.com:192.168.0.116"`
@seanzamora commented on GitHub (Aug 25, 2024): I resolved this issue by setting extra_hosts domain to point to Hosts serve private IP for example: 192.168.0.116. ` extra_hosts: - "netbird.example.com:192.168.0.116"`
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 triage-needed
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#698
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?