Error: no valid addresses were provided for transports

[icidasset]

👋 Thanks for the 0.41.0 update!

I'm having an issue with upgrading from 0.38
I'm getting the following error:

Error: no valid addresses were provided for transports [WebSockets,WebRTCStar,Circuit]

I'm setting it up as follows, which worked before the upgrade:

const ipfs = await Ipfs.create();
await ipfs.swarm.connect("/dns4/ipfs.runfission.com/tcp/4003/wss/ipfs/QmVLEz2SxoNiFnuyLpbXsH6SvjPTrHNMU88vCQZyhgBzgw")

Any thoughts on what changed?

[alanshaw]

Are you running in Node.js or the browser or somewhere else? What swarm addresses do you have configured? ipfs.config.get(‘Addresses.Swarm’). I’m guessing you have a websocket-star address or something in there.

[icidasset]

I found the "issue" 😅

I'm connecting to a peer (swarm) after I called create. But, I got the error immediately after calling create without any configuration (ie. just Ipfs.create())

If I pass an empty swarm list to create, as follows, it does work:

Ipfs.create({ config: { Addresses: { Swarm: [] } } })
await ipfs.swarm.connect(...)

Previously I didn't have to pass this empty list to create. What do you think @alanshaw? Is the new behaviour better, is this confusing, is this just edge-case, or am I not using this as intended?

Thanks ✌️

PS. I'm running this in the browser using the minified unpkg distribution.

[alanshaw]

I think by using that config you removed the websocket-star address you previously had saved in Addresses.Swarm so there was no longer an address without a transport.

@jacobheun do you think this startup error should be downgraded to a warning?

[jacobheun]

@alanshaw yes, I think so, this shouldn't be a fatal error. The available startup addresses don't have any transports so it will fail to connect, however, performing a manual connect will still work.

The important thing to note is that your node will be dial only.

We need to make this a configurable option in libp2p in case people want the overt error, but we can configure js-ipfs (node, browser or both) to be more lenient. I created an issue in libp2p, libp2p/js-libp2p#575, to track this.

[woss]

im having this issue in 0.41.2 version. what is the solution, how can i use swarm addresses?

[vasco-santos]

FYI, I will be working on the libp2p/js-libp2p#575 next week. We aim to get a better explanation for this error and configure it to be more lenient.

@woss regarding your issue. You are probably using a websocket-star address, which we do not support anymore. Since it it possibly the unique multiaddr you are providing, it will fail to listen in any of the libp2p transports.

For now, if you want to use ipfs in a browser environment, you should rely on webrtc-star. Over the next months, I plan to work on other solutions for improving ipfs connectivity in tge browser.

[5310]

@vasco-santos on a small tangent, is there any way to tell if the /dns4/star-signal.cloud.ipfs.team/wss/p2p-webrtc-star webrtc-star signalling dev-server is alive or not?

[achingbrain]

@5310 you should try to connect to it and handle the failure if it doesn't work. Better yet, stand up your own signalling server which you can guarantee is available, not under heavy load, etc and use that.

Take a look at the webrtc-star readme: https://github.com/libp2p/js-libp2p-webrtc-star#rendezvous-server-aka-signalling-server

[vasco-santos]

@5310 as @achingbrain recommended, the best solution is to run your own signalling server. We want to update the available public signalling servers and increase their redundancy, but they should only be used for demos and examples purposes, since there is no guarantee on availability.

[5310]

Right now I do have a local WebRTC-Star signaling server that I use for testing. But the public server was pretty nifty for Codepen demos. I've actually not caught it up even once all year, even though it seemed to not have been discontinued just yet from the docs.

The existence of WebRTC-Stardust also made things a bit confusing, but I guess it's not ready yet. Will try to host a remotely accessible signaling server for my demos. 👍

[jacobheun]

As part of this we need to get a webrtc-star server deployed to replace the websocket-star server, tracking this at libp2p/js-libp2p-webrtc-star#180.