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

Error while connecting peer #31

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

Originally created by @bharathmsd7 on GitHub (Jul 12, 2021).

Trying to connect peer using cmd
sudo wiretrustee add-peer --allowedIPs 10.30.30.2/32 --key '<PEER2 PUBLIC KEY>'

ERROR :
received a new message from Peer [fingerprint: peer1 publickey]"
error while handling message of Peer [key: ] error: [wrongly addressed message ]

Originally created by @bharathmsd7 on GitHub (Jul 12, 2021). Trying to connect peer using cmd `sudo wiretrustee add-peer --allowedIPs 10.30.30.2/32 --key '<PEER2 PUBLIC KEY>'` ERROR : received a new message from Peer [fingerprint: peer1 publickey]" error while handling message of Peer [key: <peer1 publickey>] error: [wrongly addressed message <peer1 publickey>]
saavagebueno commented 2025-11-20 05:05:12 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Jul 12, 2021):

Hey, could you please provide the contents of /etc/wiretrustee/config.json of both peers?

Important! Please remove private keys from the config.json before pasting the contents.

Thank you.

@braginini commented on GitHub (Jul 12, 2021): Hey, could you please provide the contents of /etc/wiretrustee/config.json of both peers? **Important!** Please remove private keys from the config.json before pasting the contents. Thank you.
saavagebueno commented 2025-11-20 05:05:12 -05:00
Author
Owner
Copy Link

@bharathmsd7 commented on GitHub (Jul 12, 2021):

Peer 1 :
{"PrivateKey":"privatekey","Peers":[{"WgPubKey":"publickey","WgAllowedIps":"10.30.30.2/32"}],"StunTurnURLs":[{"Scheme":1,"Host":"stun.wiretrustee.com","Port":3468,"Username":"","Password":"","Proto":1},{"Scheme":1,"Host":"stun.l.google.com","Port":19302,"Username":"","Password":"","Proto":1},{"Scheme":3,"Host":"stun.wiretrustee.com","Port":3468,"Username":"username1","Password":"password1","Proto":1}],"SignalAddr":"signal.wiretrustee.com:10000","WgAddr":"10.30.30.1/24","WgIface":"wiretrustee0","IFaceBlackList":null}

Peer 2 :
{"PrivateKey":"privatekey","Peers":null,"StunTurnURLs":[{"Scheme":1,"Host":"stun.wiretrustee.com","Port":3468,"Username":"","Password":"","Proto":1},{"Scheme":1,"Host":"stun.l.google.com","Port":19302,"Username":"","Password":"","Proto":1},{"Scheme":3,"Host":"stun.wiretrustee.com","Port":3468,"Username":"username1","Password":"password1","Proto":1}],"SignalAddr":"signal.wiretrustee.com:10000","WgAddr":"10.30.30.2/24","WgIface":"wiretrustee0","IFaceBlackList":null}

@bharathmsd7 commented on GitHub (Jul 12, 2021): Peer 1 : {"PrivateKey":"privatekey","Peers":[{"WgPubKey":"publickey","WgAllowedIps":"10.30.30.2/32"}],"StunTurnURLs":[{"Scheme":1,"Host":"stun.wiretrustee.com","Port":3468,"Username":"","Password":"","Proto":1},{"Scheme":1,"Host":"stun.l.google.com","Port":19302,"Username":"","Password":"","Proto":1},{"Scheme":3,"Host":"stun.wiretrustee.com","Port":3468,"Username":"username1","Password":"password1","Proto":1}],"SignalAddr":"signal.wiretrustee.com:10000","WgAddr":"10.30.30.1/24","WgIface":"wiretrustee0","IFaceBlackList":null} Peer 2 : {"PrivateKey":"privatekey","Peers":null,"StunTurnURLs":[{"Scheme":1,"Host":"stun.wiretrustee.com","Port":3468,"Username":"","Password":"","Proto":1},{"Scheme":1,"Host":"stun.l.google.com","Port":19302,"Username":"","Password":"","Proto":1},{"Scheme":3,"Host":"stun.wiretrustee.com","Port":3468,"Username":"username1","Password":"password1","Proto":1}],"SignalAddr":"signal.wiretrustee.com:10000","WgAddr":"10.30.30.2/24","WgIface":"wiretrustee0","IFaceBlackList":null}
saavagebueno commented 2025-11-20 05:05:12 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Jul 12, 2021):

Thanks.

It seems like you haven't run on the the Peer 2
sudo wiretrustee add-peer --allowedIPs 10.30.30.1/32 --key '<PEER1 PUBLIC KEY>'

This is required in order Wireguard on Peer 2 accept requests from the Peer 1

P.S. we plan to release a peer management system soon so these kind of issues will be obsolete.

Let me know if it helped!

@braginini commented on GitHub (Jul 12, 2021): Thanks. It seems like you haven't run on the the Peer 2 `sudo wiretrustee add-peer --allowedIPs 10.30.30.1/32 --key '<PEER1 PUBLIC KEY>'` This is required in order Wireguard on Peer 2 accept requests from the Peer 1 P.S. we plan to release a peer management system soon so these kind of issues will be obsolete. Let me know if it helped!
saavagebueno commented 2025-11-20 05:05:13 -05:00
Author
Owner
Copy Link

@bharathmsd7 commented on GitHub (Jul 12, 2021):

That helped me man, I am new to this tool.
Thanks for the help.

@bharathmsd7 commented on GitHub (Jul 12, 2021): That helped me man, I am new to this tool. Thanks for the help.
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#31
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?