Js-ipfs: Browser Uncaught Error: no protocol with name: p2p-webrtc-star

Created on 4 Sep 2017  路  3Comments  路  Source: ipfs/js-ipfs

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

Most helpful comment

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

All 3 comments

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

you need more bootstrap nodes for resilience

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

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

Was this page helpful?
0 / 5 - 0 ratings