IPFS setup sometimes fails

[icidasset]

Browser: Firefox 81
OS: MacOS 11

Looks like the websocket connection fails and IPFS fails to start, causing initialise to fail entirely.

[icidasset]

Safari:

[bmann]

I don’t think we should be including content from CDNs for stuff that is core to us. I don’t know if that is the issue, but that jumps out at me from the screenshot.

[icidasset]

@bmann Nah, nothing to do with the issue, the issue is with web sockets (which can identified by the ws:// and wss:// protocols). But yeah, you're right, shouldn't rely on cdns (although we are caching it in case the cdn isn't available).

[icidasset]

Semi-related: The ws warnings/errors (note, not wss) should go away with the next libp2p release: ipfs/js-ipfs#3298

[icidasset]

Ah, found related issues on js-libp2p and js-ipfs:
libp2p/js-libp2p#312
ipfs/js-ipfs#1837

[icidasset]

I'm thinking this fails in IPFS itself, because our gateway is on the bootstrap list.
Could also come from the swarm.connect which is done right after the IPFS setup.

I'm not sure we need that swarm.connect there 🤔
I would think being in the bootstrap list automatically connects to that address.
Which is what I do on the lobby.

See https://github.com/fission-suite/webnative/blob/44d6a864c771f9d8b8f14acc408d239e67e428af/src/ipfs/config.ts#L51

Thoughts @dholms ?

[icidasset]

Wrote a reconnect script for this.