Websocket error when ws-star.discovery.libp2p.io connection fails

[olizilla]

Posting this here for visibility.

See:

• Handle IPFS init error if ws-star.discovery.libp2p.io connection fails ipfs-shipyard/peer-pad-core#13
• batter asynchronous error handling #114

[pgte]

@lgierth Could we have an instance dedicated to peer-pad?

[ghost]

@victorbjelkholm is working on one

[victorb]

Indeed! Current testing multiaddr is /dns4/ws-star0.lon.dwebops.pub/tcp/443/wss/p2p-websocket-star. Once we're 100% everthing is working fine and have better metrics/monitoring in place, I'll switch the records so ws-star.discovery.libp2p.io points to the new one.

[victorb]

It has now been deployed to ws-star.discovery.libp2p.io. But there is not a dedicated one for peerpad, missed that point last time I read this issue. Will create a new one for just peerpad.

[pgte]

@victorbjelkholm not sure if in flux, but I tried using /dns4/ws-star0.lon.dwebops.pub/tcp/443/wss/p2p-websocket-star in PeerPad and I couldn't connect.