WebSocket Error wss://ws-star.discovery.libp2p.io/socket.io

[maxkerp]

Hi there :)

I'm currently working on my bachelor's thesis in which I proof that creating WebComponents using OrbitDB is possible. OrbitDB uses ipfs and its experimental pubsub feature, including the transport over WebSockets.

Addresses: {
  Swarm: [
    // Use IPFS dev signal server
    // '/dns4/star-signal.cloud.ipfs.team/wss/p2p-webrtc-star',
    '/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star',
    // Use local signal server
    // '/ip4/127.0.0.1/tcp/1337/ws/p2p-webrtc-star'
  ]
}

In the last couple of days I'm getting a lot of Errors when creating the ipfs node in the browser. WebSocket connection to 'wss://ws-star.discovery.libp2p.io/socket.io/?EIO=3&transport=websocket' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED.

My guess is that the traffic to this endpoint is getting pretty big. Are there any resources on how to setting up an own signaling server? My Professor is really interested in ipfs and its possibilities.
It might be possible to get a signaling server up and running at my college, maybe even a mirror of your whole setup to increase stability.

Any help is much appreciated :)

[sriharrsha]

I'm on 0.33.1

Never used wss1 or wss0 but somewhere the dependency libraries are hardcoded calling these servers.

Any Help?

[mizchi]

Same here with [email protected] (wss://sgp-1.bootstrap.libp2p.io/)

[mkg20001]

Btw, this should be moved to the ws-star repo as this isn't about libp2p-websockets

[Juanperezc]

Same issue when I use [email protected]

[Tryptophan]

Same issue here with [email protected].

[Juanperezc]

Guys ws-star.discovery.libp2p.io/socket.io is down

[sriharrsha]

It is wss1 not ws-star. I figured out it is because of the cache somewhere in the older installation which is not overriden by the config.
When I tried on a fresh computer & browser this error didn't come up. So I reinstalle my browser an it vanished. There has to be a way when we update the packages to make it backward compatible.

[Tryptophan]

@Juanperezc is there a way to check the status of this discovery node? I've been retrying for the past day with no ability to connect.

[hushino]

same error with ipfs 0.33.1, node 10.14.2 and npm 6.5,

websocket.js:110 WebSocket connection to 'wss://ws-star.discovery.libp2p.io/socket.io/?EIO=3&transport=websocket' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

transport.js:67 Uncaught Error: websocket error
at WS.Transport.onError (transport.js:67)
at WebSocket.ws.onerror (websocket.js:148)

[jazz7381]

you need to open the web with https

[achingbrain]

This issue is about ws-star which is no longer supported since better methods of peer discovery are now available, consequently the ws-star.discovery.libp2p.io nodes have long been retired.

For peer discovery the DHT can now be used instead.