SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-01 02:18:39 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Signal didnt receive a registration header #943

New Issue
Open
opened 2025-11-20 05:20:21 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:20:21 -05:00
Owner
Copy Link

Originally created by @MichalNemec on GitHub (May 30, 2024).

Describe the problem

No header sent from signal

To Reproduce

Steps to reproduce the behavior:

  1. default netbird self hosted
  2. keycloak
  3. nginx proxy

Expected behavior

signal should work properly

Are you using NetBird Cloud?

NetBird version

0.27.10

NetBird status -d output:

Screenshots

Additional context

sudo netbird up -F --log-level debug --setup-key DC5D5E9B-52B4-485E-B440-9918F49D9C7C --management-url https://vpn.domain.com:33073
2024-05-31T04:49:08+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.domain.com:33073
2024-05-31T04:49:09+02:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.domain.com:33073
2024-05-31T04:49:10+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.domain.com:33073
2024-05-31T04:49:11+02:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.domain.com:33073
2024-05-31T04:49:12+02:00 INFO client/internal/connect.go:119: starting NetBird client version 0.27.10 on darwin/arm64
2024-05-31T04:49:12+02:00 DEBG client/internal/connect.go:180: connecting to the Management service vpn.domain.com:33073
2024-05-31T04:49:12+02:00 DEBG client/internal/connect.go:188: connected to the Management service vpn.domain.com:33073
2024-05-31T04:49:14+02:00 DEBG signal/client/grpc.go:92: connected to Signal Service: vpn.domain.com:443
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for 0.0.0.0: interface &{26 1500 bridge100 d6:57:63:3d:24:64 up|broadcast|multicast|running} nexthop <nil>, preferred source 192.168.64.1
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:88: No next hop found for ip 0.0.0.0, using preferred source 192.168.64.1
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for ::: interface &{21 1380 utun5  up|pointtopoint|multicast|running} nexthop fe80::, preferred source fe80::a4db:6535:d476:7cd3
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 0 for prefix IP/32
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:56: Adding route for prefix IP/32
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for IP: interface &{12 1500 en0 d4:57:63:d3:05:74 up|broadcast|multicast|running} nexthop 192.168.0.1, preferred source 192.168.0.116
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:171: Found next hop 192.168.0.1 for prefix IP/32 with interface &{12 1500 en0 d4:57:63:d3:05:74 up|broadcast|multicast|running}
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:187: Adding a new route for prefix IP/32 with next hop 192.168.0.1
2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 1 for prefix IP/32
2024-05-31T04:49:14+02:00 INFO client/internal/routemanager/manager.go:93: Routing setup complete
2024-05-31T04:49:14+02:00 DEBG iface/wg_configurer_usp.go:37: adding Wireguard private key
2024-05-31T04:49:14+02:00 DEBG iface/tun_darwin.go:82: device is ready to use: utun100
2024-05-31T04:49:14+02:00 DEBG signal/client/grpc.go:137: signal connection state READY
2024-05-31T04:50:14+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams
2024-05-31T04:50:15+02:00 DEBG signal/client/grpc.go:137: signal connection state READY
2024-05-31T04:51:15+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams
2024-05-31T04:51:16+02:00 DEBG signal/client/grpc.go:137: signal connection state READY
2024-05-31T04:52:17+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams
2024-05-31T04:52:17+02:00 DEBG signal/client/grpc.go:137: signal connection state READY
Originally created by @MichalNemec on GitHub (May 30, 2024). **Describe the problem** No header sent from signal **To Reproduce** Steps to reproduce the behavior: 1. default netbird self hosted 2. keycloak 3. nginx proxy **Expected behavior** signal should work properly **Are you using NetBird Cloud?** - **NetBird version** 0.27.10 **NetBird status -d output:** - **Screenshots** - **Additional context** ``` sudo netbird up -F --log-level debug --setup-key DC5D5E9B-52B4-485E-B440-9918F49D9C7C --management-url https://vpn.domain.com:33073 2024-05-31T04:49:08+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.domain.com:33073 2024-05-31T04:49:09+02:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.domain.com:33073 2024-05-31T04:49:10+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://vpn.domain.com:33073 2024-05-31T04:49:11+02:00 DEBG client/internal/login.go:63: connected to the Management service https://vpn.domain.com:33073 2024-05-31T04:49:12+02:00 INFO client/internal/connect.go:119: starting NetBird client version 0.27.10 on darwin/arm64 2024-05-31T04:49:12+02:00 DEBG client/internal/connect.go:180: connecting to the Management service vpn.domain.com:33073 2024-05-31T04:49:12+02:00 DEBG client/internal/connect.go:188: connected to the Management service vpn.domain.com:33073 2024-05-31T04:49:14+02:00 DEBG signal/client/grpc.go:92: connected to Signal Service: vpn.domain.com:443 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for 0.0.0.0: interface &{26 1500 bridge100 d6:57:63:3d:24:64 up|broadcast|multicast|running} nexthop <nil>, preferred source 192.168.64.1 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:88: No next hop found for ip 0.0.0.0, using preferred source 192.168.64.1 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for ::: interface &{21 1380 utun5 up|pointtopoint|multicast|running} nexthop fe80::, preferred source fe80::a4db:6535:d476:7cd3 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 0 for prefix IP/32 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:56: Adding route for prefix IP/32 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:83: Route for IP: interface &{12 1500 en0 d4:57:63:d3:05:74 up|broadcast|multicast|running} nexthop 192.168.0.1, preferred source 192.168.0.116 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:171: Found next hop 192.168.0.1 for prefix IP/32 with interface &{12 1500 en0 d4:57:63:d3:05:74 up|broadcast|multicast|running} 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/systemops.go:187: Adding a new route for prefix IP/32 with next hop 192.168.0.1 2024-05-31T04:49:14+02:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 1 for prefix IP/32 2024-05-31T04:49:14+02:00 INFO client/internal/routemanager/manager.go:93: Routing setup complete 2024-05-31T04:49:14+02:00 DEBG iface/wg_configurer_usp.go:37: adding Wireguard private key 2024-05-31T04:49:14+02:00 DEBG iface/tun_darwin.go:82: device is ready to use: utun100 2024-05-31T04:49:14+02:00 DEBG signal/client/grpc.go:137: signal connection state READY 2024-05-31T04:50:14+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams 2024-05-31T04:50:15+02:00 DEBG signal/client/grpc.go:137: signal connection state READY 2024-05-31T04:51:15+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams 2024-05-31T04:51:16+02:00 DEBG signal/client/grpc.go:137: signal connection state READY 2024-05-31T04:52:17+02:00 WARN signal/client/grpc.go:152: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams 2024-05-31T04:52:17+02:00 DEBG signal/client/grpc.go:137: signal connection state READY ```
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:20:21 -05:00
saavagebueno commented 2025-11-20 05:20:21 -05:00
Author
Owner
Copy Link

@TheRealGramdalf commented on GitHub (Jul 23, 2024):

I had this exact issue, in my case it was that the netbird-signal service wasn't proxied correctly. I use traefik, and while messing around with things I must have accidentally left an entrypoint: directive (essentially listen address) where I didn't mean to.

For reference, heres my current server config. Make sure the signal service is accessible on your https://domain.example.com:443 externally, not :80 or something like that.

@TheRealGramdalf commented on GitHub (Jul 23, 2024): I had this exact issue, in my case it was that the `netbird-signal` service wasn't proxied correctly. I use traefik, and while messing around with things I must have accidentally left an `entrypoint:` directive (essentially listen address) where I didn't mean to. For reference, [heres](https://github.com/TheRealGramdalf/nixos/blob/52dedea90c1bdb84e340c45620c699c8deae8eff/config/hosts/aer/services/netbird.nix) my current server config. Make sure the signal service is accessible on your `https://domain.example.com:443` externally, not `:80` or something like that.
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@IKA3RUS commented on GitHub (Sep 28, 2024):

I got the same error too with traefik. In my case, the issue was the Signal block in management.json had the port mentioned as :80 instead of the expected :443 - most probably because I must have accidentally changed NETBIRD_SIGNAL_PORT to 80 in the setup.env while setting it all up.

This is how the Signal block in management.json should look like

    "Signal": {
        "Proto": "https",
        "URI": "netbird.yourdomain.com:443",
        "Username": "",
        "Password": null
    },
@IKA3RUS commented on GitHub (Sep 28, 2024): I got the same error too with traefik. In my case, the issue was the Signal block in `management.json` had the port mentioned as `:80` instead of the expected `:443` - most probably because I must have accidentally changed `NETBIRD_SIGNAL_PORT` to `80` in the `setup.env` while setting it all up. This is how the Signal block in `management.json` should look like ``` "Signal": { "Proto": "https", "URI": "netbird.yourdomain.com:443", "Username": "", "Password": null }, ```
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

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

Hello @MichalNemec,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @MichalNemec, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:20:22 -05:00
Author
Owner
Copy Link

@MichalNemec commented on GitHub (Apr 28, 2025):

lately i dont have any issues.

@MichalNemec commented on GitHub (Apr 28, 2025): lately i dont have any issues.
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 waiting-feedback
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#943
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?