Replies: 1 comment 1 reply
-
I think it means your browser is failing to resolve the domain name of the configured servers. There's an
I don't know if including the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In the universal-connectivity, we initialise the webrtc transport in js-libp2p as follows:
When I initiate a WebRTC connection from the browser to another browser peer with the following multiaddr:
/ip4/147.28.186.157/udp/9090/webrtc-direct/certhash/uEiBbC9bbdvraVWDvcvCEdJAWDymmUqiJQ964FuyEq0hELw/p2p/12D3KooWGahRw3ZnM4gAyd9FK75v4Bp5keFYTvkcAwhpEm28wbV3/p2p-circuit/webrtc/p2p/12D3KooWNuYo4UdN3eomAngE4DPRwVz5qXxLQsa6njw1TjFJZsNb
, I noticed that I get the following error:What's the exact meaning of this error?
What are some good ways to get a better understanding and debug the state of a webrtc connection?
I should note that this is a connection between two browsers on the same machine and the connection is upgraded successfully to a direct connection.
Beta Was this translation helpful? Give feedback.
All reactions