[GH-ISSUE #48] Error while connecting peer #143

Closed
opened 2026-08-05 00:37:25 -04:00 by saavagebueno · 4 comments
Owner

Originally created by @bharathmsd7 on GitHub (Jul 12, 2021).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/48

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). Original GitHub issue: https://github.com/netbirdio/netbird/issues/48 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>]
Author
Owner

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

<!-- gh-comment-id:878227590 --> @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.
Author
Owner

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

<!-- gh-comment-id:878230626 --> @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}
Author
Owner

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

<!-- gh-comment-id:878236508 --> @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!
Author
Owner

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

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

<!-- gh-comment-id:878239268 --> @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 Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#143