Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Browser Uncaught Error: no protocol with name: p2p-webrtc-star #990

Closed
ya7ya opened this issue Sep 4, 2017 · 3 comments
Closed

Browser Uncaught Error: no protocol with name: p2p-webrtc-star #990

ya7ya opened this issue Sep 4, 2017 · 3 comments

Comments

@ya7ya
Copy link
Contributor

ya7ya commented Sep 4, 2017

  • Version: 0.25.4
  • Platform: Chrome , firefox
  • Subsystem: multiaddrs , libp2p-webrtc-star

Type: Bug

Severity: High

Description: new Uncaught Error that might be related to #984

Uncaught Error: no protocol with name: p2p-webrtc-star
    at Protocols (index.min.js:24)
    at stringToStringTuples (index.min.js:217)
    at stringToBuffer (index.min.js:217)
    at Object.fromString (index.min.js:217)
    at new Multiaddr (index.min.js:4)
    at Multiaddr (index.min.js:4)
    at WebRTCStar._peerDiscovered (index.min.js:211)
    at Socket.Emitter.emit (index.min.js:5)
    at Socket.onevent (index.min.js:55)
    at Socket.onpacket (index.min.js:55)

Steps to reproduce the error:

This appears whenever IPFS is running in the browser with WebRTC enabled.
You can test it via exchange-file example.

@Komhar
Copy link

Komhar commented Sep 4, 2017

WebSocket connection to 'wss://ams-1.bootstrap.libp2p.io/' failed: Error during WebSocket handshake: Unexpected response code: 502
module.exports @ unpkg.com/ipfs@0.25.4/dist/index.min.js:220

you need more bootstrap nodes for resilience

@ya7ya
Copy link
Contributor Author

ya7ya commented Sep 4, 2017

Okay, The issue is no longer there after a fresh npm install . closing.

@ya7ya ya7ya closed this as completed Sep 4, 2017
@konsumer
Copy link

It seems to still be an issue with the CDN version. I am noticing error on orbit.chat and my codepen

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants