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

Relay signature Verfication Failed after updating Openwrt client to 0.30.3-r1 #1544

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

Originally created by @rudradevpal on GitHub (Jan 7, 2025).

I am facing issue after updating Client(Openwrt 0.30.3-r1 from 0.24.3)

Current Server Version 0.35.2

2025-01-07T15:59:56Z INFO client/internal/connect.go:111: starting NetBird client version 0.30.3 on linux/mipsle
2025-01-07T15:59:57Z INFO client/internal/connect.go:240: connecting to the Relay service(s): rel://netbird.example.com:33080
2025-01-07T15:59:57Z INFO relay/client/picker.go:66: try to connecting to relay server: rel://netbird.example.com:33080
2025-01-07T15:59:57Z INFO [relay: rel://netbird.example.com:33080] relay/client/client.go:166: create new relay connection: local peerID: 1H8swdO5hEhBj5sJD84XOqIGCMSIKWhl0=, local peer hashedID: sha-+47a3HtvT19y7bKEB7fiFP1I=
2025-01-07T15:59:57Z INFO [relay: rel://netbird.example.com:33080] relay/client/client.go:172: connecting to relay server
2025-01-07T15:59:58Z ERRO [relay: rel://netbird.example.com:33080] relay/client/client.go:301: failed to read auth response: failed to get reader: failed to read frame header: EOF
2025-01-07T15:59:58Z ERRO client/internal/connect.go:242: failed to connect to any relay server: all attempts failed
2025-01-07T16:00:01Z INFO client/internal/connect.go:240: connecting to the Relay service(s): rel://netbird.example.com:33080

2025-01-07T15:59:58Z ERRO [relay: rel://netbird.example.com:33080] relay/client/client.go:301: failed to read auth response: failed to get reader: failed to read frame header: EOF
2025-01-07T15:59:58Z ERRO client/internal/connect.go:242: failed to connect to any relay server: all attempts failed

In the relay server logs

2025-01-07T15:41:48Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-+47a3HtvjA7k535vfwT19y7bKEB7fiFP1I= (XX.XX.XX.XX:45260): invalid signature
2025-01-07T15:42:01Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-/QniPM3G1PlPjz5HLaTHN79SmN9ALAr7P0= (XX.XX.XX.XX:44042): invalid signature
2025-01-07T15:42:04Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-+47a3HtvjA7k535vcf86wT1rthB7fiFP1I= (XX.XX.XX.XX:41832): invalid signature

Originally created by @rudradevpal on GitHub (Jan 7, 2025). I am facing issue after updating Client(Openwrt 0.30.3-r1 from 0.24.3) Current Server Version 0.35.2 2025-01-07T15:59:56Z INFO client/internal/connect.go:111: starting NetBird client version 0.30.3 on linux/mipsle 2025-01-07T15:59:57Z INFO client/internal/connect.go:240: connecting to the Relay service(s): rel://netbird.example.com:33080 2025-01-07T15:59:57Z INFO relay/client/picker.go:66: try to connecting to relay server: rel://netbird.example.com:33080 2025-01-07T15:59:57Z INFO [relay: rel://netbird.example.com:33080] relay/client/client.go:166: create new relay connection: local peerID: 1H8swdO5hEhBj5sJD84XOqIGCMSIKWhl0=, local peer hashedID: sha-+47a3HtvT19y7bKEB7fiFP1I= 2025-01-07T15:59:57Z INFO [relay: rel://netbird.example.com:33080] relay/client/client.go:172: connecting to relay server 2025-01-07T15:59:58Z ERRO [relay: rel://netbird.example.com:33080] relay/client/client.go:301: failed to read auth response: failed to get reader: failed to read frame header: EOF 2025-01-07T15:59:58Z ERRO client/internal/connect.go:242: failed to connect to any relay server: all attempts failed 2025-01-07T16:00:01Z INFO client/internal/connect.go:240: connecting to the Relay service(s): rel://netbird.example.com:33080 2025-01-07T15:59:58Z ERRO [relay: rel://netbird.example.com:33080] relay/client/client.go:301: failed to read auth response: failed to get reader: failed to read frame header: EOF 2025-01-07T15:59:58Z ERRO client/internal/connect.go:242: failed to connect to any relay server: all attempts failed In the relay server logs 2025-01-07T15:41:48Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-+47a3HtvjA7k535vfwT19y7bKEB7fiFP1I= (XX.XX.XX.XX:45260): invalid signature 2025-01-07T15:42:01Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-/QniPM3G1PlPjz5HLaTHN79SmN9ALAr7P0= (XX.XX.XX.XX:44042): invalid signature 2025-01-07T15:42:04Z ERRO relay/server/relay.go:121: failed to handshake: validate sha-+47a3HtvjA7k535vcf86wT1rthB7fiFP1I= (XX.XX.XX.XX:41832): invalid signature
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:32:32 -05:00
saavagebueno commented 2025-11-20 05:32:33 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jan 7, 2025):

Hello @rudradevpal, Can you confirm that your relay server is also running a recent version?

Besides that, the community maintained packages feed is already deploying the 0.35.2 version: https://github.com/openwrt/packages/blob/master/net/netbird/Makefile

Can you upgrade your client to that version?

@mlsmaycon commented on GitHub (Jan 7, 2025): Hello @rudradevpal, Can you confirm that your relay server is also running a recent version? Besides that, the community maintained packages feed is already deploying the 0.35.2 version: https://github.com/openwrt/packages/blob/master/net/netbird/Makefile Can you upgrade your client to that version?
saavagebueno commented 2025-11-20 05:32:33 -05:00
Author
Owner
Copy Link

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

Hello @rudradevpal,

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 @rudradevpal, 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:32:34 -05:00
Author
Owner
Copy Link

@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.

@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.
saavagebueno commented 2025-11-20 05:32:34 -05:00
Author
Owner
Copy Link

@nmapx commented on GitHub (Aug 13, 2025):

@mlsmaycon @nazarewk I'm having the same issue on ver. 0.54.2

Relay service logs:

2025-08-13T21:31:28Z INFO relay/server/listener/ws/listener.go:100: WS client connected from: 172.20.13.1:47978
2025-08-13T21:31:28Z ERRO relay/server/relay.go:123: failed to handshake: validate sha-jUr0bSxRb/VFaIwkYW+tKkredcJVKIUYH5HOPBQG3oc= (172.20.13.1:47978): invalid signature

Client logs:

2025-08-13T23:31:30+02:00 INFO [relay: rels://my.proxy.com:443/relay] shared/relay/client/dialer/race_dialer.go:91: successfully dialed via: WS
2025-08-13T23:31:30+02:00 ERRO [relay: rels://my.proxy.com:443/relay] shared/relay/client/client.go:329: failed to read auth response: failed to get reader: failed to read frame header: EOF
2025-08-13T23:31:30+02:00 ERRO shared/relay/client/guard.go:59: failed to pick new Relay server: failed to connect to any relay server: all attempts failed

Rest of the config is similar to the one mentioned here: https://github.com/netbirdio/netbird/issues/536#issuecomment-2409099492

Everything running in docker containers.
I'm proxying websocket /relay endpoint to relay service using NPM (hardcore stuff 😅)
What am I missing? Please assist 🥺

Tested /relay endpoint with curl with following results:

❯ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Key: 4q7lRojWTCV6S7z2Y0nAlA==" -H "Sec-WebSocket-Version: 13" https://my.proxy.com/relay
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
❯ curl -i -N --http1.1 -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Key: 4q7lRojWTCV6S7z2Y0nAlA==" -H "Sec-WebSocket-Version: 13" https://my.proxy.com/relay
HTTP/1.1 101 Switching Protocols
Server: openresty
Date: Thu, 14 Aug 2025 10:21:09 GMT
Connection: upgrade
Sec-Websocket-Accept: Xy+AkRHCPd6+FTRCkBuQ8HqQ3uc=
Upgrade: websocket

^C
@nmapx commented on GitHub (Aug 13, 2025): @mlsmaycon @nazarewk I'm having the same issue on ver. `0.54.2` Relay service logs: ``` 2025-08-13T21:31:28Z INFO relay/server/listener/ws/listener.go:100: WS client connected from: 172.20.13.1:47978 2025-08-13T21:31:28Z ERRO relay/server/relay.go:123: failed to handshake: validate sha-jUr0bSxRb/VFaIwkYW+tKkredcJVKIUYH5HOPBQG3oc= (172.20.13.1:47978): invalid signature ``` Client logs: ``` 2025-08-13T23:31:30+02:00 INFO [relay: rels://my.proxy.com:443/relay] shared/relay/client/dialer/race_dialer.go:91: successfully dialed via: WS 2025-08-13T23:31:30+02:00 ERRO [relay: rels://my.proxy.com:443/relay] shared/relay/client/client.go:329: failed to read auth response: failed to get reader: failed to read frame header: EOF 2025-08-13T23:31:30+02:00 ERRO shared/relay/client/guard.go:59: failed to pick new Relay server: failed to connect to any relay server: all attempts failed ``` Rest of the config is similar to the one mentioned here: https://github.com/netbirdio/netbird/issues/536#issuecomment-2409099492 Everything running in docker containers. I'm proxying websocket /relay endpoint to relay service using NPM (hardcore stuff 😅) What am I missing? Please assist 🥺 Tested /relay endpoint with curl with following results: ``` ❯ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Key: 4q7lRojWTCV6S7z2Y0nAlA==" -H "Sec-WebSocket-Version: 13" https://my.proxy.com/relay curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1) ❯ curl -i -N --http1.1 -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Key: 4q7lRojWTCV6S7z2Y0nAlA==" -H "Sec-WebSocket-Version: 13" https://my.proxy.com/relay HTTP/1.1 101 Switching Protocols Server: openresty Date: Thu, 14 Aug 2025 10:21:09 GMT Connection: upgrade Sec-Websocket-Accept: Xy+AkRHCPd6+FTRCkBuQ8HqQ3uc= Upgrade: websocket ^C ```
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#1544
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?