Skip to content
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

Errors connecting to WebRTC-direct multiaddrs #2805

Open
2color opened this issue Nov 5, 2024 · 2 comments
Open

Errors connecting to WebRTC-direct multiaddrs #2805

2color opened this issue Nov 5, 2024 · 2 comments
Assignees
Labels
kind/bug A bug in existing code (including security flaws) status/in-progress In progress

Comments

@2color
Copy link
Contributor

2color commented Nov 5, 2024

Description

Problems connecting to public peers with WebRTC-direct in Chrome, Firefox, and Safari. I tried with known peers such as the public bootstrappers and still got errors. Both

In Chrome, the error I get is:

WebRTC transport error: [stream: data] data channel error: Data channel was never opened: state: connecting

In Firefox:

libp2p:connection-manager:dial-queue:error dial failed to /ip4/147.28.186.157/udp/9095/webrtc-direct/certhash/uEiAPnDhaUxscuBMco2KQMGUxtpGZin9vP7UV2S6KJMtShA/p2p/12D3KooWFhXabKDwALpzqMbto94sB7rvmZ6M28hs9Y9xSopDKwQr +0ms WebRTC/DataChannelError: WebRTC transport error: [stream: data] data channel error: Data channel was never opened: state: connecting

Safari:

WebRTC/DataChannelError: WebRTC transport error: [stream: data] data channel error: Data channel was never opened: state: connecting

Specific multiaddrs with problems

// ([go-libp2p universal-connectivity peer](https://github.com/libp2p/universal-connectivity/tree/main/go-peer))
/ip4/147.28.186.157/udp/9095/webrtc-direct/certhash/uEiAPnDhaUxscuBMco2KQMGUxtpGZin9vP7UV2S6KJMtShA/p2p/12D3KooWFhXabKDwALpzqMbto94sB7rvmZ6M28hs9Y9xSopDKwQr 

// (Kubo bootstrapper)
/ip4/147.75.87.27/udp/4001/webrtc-direct/certhash/uEiCrpessP8HCV-35Z4PrH8GByhOCHGZ5KNRDkU5xgsoE2g/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb 

// (Rust bootstrapper)
/ip4/139.178.91.71/udp/4001/webrtc-direct/certhash/uEiCob71FRmYEoCvDCnsMS1g-Za67dM4Q7tjpK9QTf59_YQ/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN 

Steps to reproduce the error

@2color 2color added the need/triage Needs initial labeling and prioritization label Nov 5, 2024
@2color
Copy link
Contributor Author

2color commented Nov 7, 2024

Interop tests are passing for WebRTC-direct between go-libp2p and Chrome:
https://github.com/libp2p/test-plans/actions/runs/11470308248/job/31919229144#step:3:2470

I was also able to successfully open a connection to a localhost webrtc-peer (https://github.com/libp2p/universal-connectivity/tree/main/go-peer)

@MarcoPolo MarcoPolo self-assigned this Nov 11, 2024
@2color
Copy link
Contributor Author

2color commented Nov 13, 2024

Related: libp2p/go-libp2p#3040

@achingbrain achingbrain added status/in-progress In progress kind/bug A bug in existing code (including security flaws) and removed need/triage Needs initial labeling and prioritization labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) status/in-progress In progress
Projects
None yet
Development

No branches or pull requests

4 participants