-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libp2p 2.4.0 No Multiaddrs after connecting to relay #2883
Comments
Please can you share your full node config? |
Sure. This is the config I use for Node A (and other peers)
And this is the config for relay NodeB
NodeB runs on a public server in a docker container. I use reverse proxy to forward the https requests to http in the container. |
After we have created a reservation on a relay, automatically confirm that it is publicly dialable. Fixes #2883
@sneaker1 does this fix provide you with the MultiAddress? I am having the same issue since some time, updated my packages but still don't see the multiaddress of a connecting peer other than the relays. Also, I use PubsubPeerDiscovery and it naturally doesn't connect the peers because of it. Can you send me the exact packages.json dependencies you are using? "@chainsafe/libp2p-gossipsub": "^14.1.0", |
Version:
libp2p 2.4.0
circuit-relay-v2 3.1.4
Platform:
Linux
Severity:
High - The main functionality of the application does not work, API breakage, repo format breakage, etc.
Description:
After upgrading from libp2p 2.3.1 to 2.4.0 i noticed that the peers in my network could not connect to each other via the relay.
Node A has the following addresses configuration:
Node A connects to a relay node B.
After connecting to the relay B, the multiaddrs of Node A are empty. In the peerstore of Node B, the entry of Node A also has no Multiaddrs.
Because of that peers can not connect to each other.
Expected Behavior:
After connecting to the relay, NodeA should get a multiaddr like this:
/dns4/relay.example.com/tcp/443/wss/p2p/QmNzZCxCahWDLSMfxouxoSikA861uvZvp32G3RJ8UNodeB/p2p-circuit/p2p/QmVyuQ4uvR9d7wnafdJYNQ1zLEzFEFvQqwUcXeoYsNodeA
The text was updated successfully, but these errors were encountered: