WebSocket connection failed, Error 403

[milankragujevic]

• Version: 0.25.1
• Platform: Browser, Windows 10, Chrome 60.0.3112.78
• Subsystem: Not sure?

Type: Bug

Severity: Medium

Description: I receive a websocket error.

VM44:161 WebSocket connection to 'wss://ams-1.bootstrap.libp2p.io/' failed: Error during WebSocket handshake: Unexpected response code: 403

Steps to reproduce the error: https://milankragujevic.com/temp/ipfs/test.html

[lightninglu10]

I'm getting the same error here. Seems like there's no error handling on a failed wss reconnect so it tries a bunch and then eventually IPFS crashes which crashes my browser.

[ghost]

Are you getting the same 403 error with other bootstrap.libp2p.io nodes too, and is this only on reconnect? I'm seeing a couple dozen peers connected to these nodes so from my point of view all is good.

[lightninglu10]

This happens to me whenever I load up my web page and I have IPFS running in the page.

[ya7ya]

I'm seeing the same issue too.

[victorb]

@lgierth some nodes seems to work, but others not...

For example, nodes I can connect to (get status code 101):

• sgp-1.bootstrap.libp2p.io
• nyc-{1,2}.bootstrap.libp2p.io
• lon-1.bootstrap.libp2p.io

Nodes that don't work (get status code 403):

• sfo-{1,3}.bootstrap.libp2p.io
• ams-1.bootstrap.libp2p.io

[ghost]

Nodes that don't work (get status code 403):

• sfo-{1,3}.bootstrap.libp2p.io
• ams-1.bootstrap.libp2p.io

Great, these are the ones running go-ipfs master using the new websocket lib :/

[victorb]

We have now rolled back the bootstrap nodes with the new websocket library so things should work correctly now.

Sorry for the temporary hiccup with this.

[milankragujevic]

Still getting a similar issue as I got before
WebSocket connection to 'wss://sfo-2.bootstrap.libp2p.io/' failed: Error during WebSocket handshake: Unexpected response code: 502

Only sfo-1 and sfo-2.

[daviddias]

@milankragujevic confirm if this makes the node unusable. If I understand correctly, the browser itself will log an error if a connection fails, which doesn't mean that all the other connections won't work.

[joeltg]

Also getting this - after a while (~5 minutes) the page crashes.

[JohnAllen]

I get exactly what @joeltg gets so won't repost unless requested. I am also unable to ipfs cat content added after this so has made IPFS in the browser not very useful for the time being.

[mitra42]

I get these errors as well, BUT not many of them and it doesn't crash the page. However - the page crashing after about 5 mins is something we are seeing all the time, and is something reported on #950 and by Orbit on #942

[lightninglu10]

@joeltg check these issues on the browser crashing.

#950

I think we solved our IPFS browser crashing issue by disabling webRTC by here: #942 (comment)

before the # of listeners continually increased, but now they stay at a reasonable state without webRTC (which is default enabled)

[merlox]

What kind of solution is that? I just can't disable webRTC because my dapp needs it.

[mitra42]

Yes - same for us, disabling WebRTC seems to disable IIIF (both PubSub and retrieving annotation lists) which means without WebRTC our demos are non-functional

[merlox]

Here is the solution for me, I removed those 2 nodes that were emmiting the error:
BEFORE:

 const ipfs = new Ipfs({
  init: true,
  start: true,
  repo: 'ipfs-testing',
  config: {
    Bootstrap: [
      "/dns4/ams-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd",
      "/dns4/sfo-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLju6m7xTh3DuokvT3886QRYqxAzb1kShaanJgW36yx",
      "/dns4/lon-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLMeWqB7YGVLJN3pNLQpmmEk35v6wYtsMGLzSr5QBU3",
      "/dns4/sfo-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLnSGccFuZQJzRadHn95W2CrSFmZuTdDWP8HXaHca9z",
      "/dns4/sfo-3.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM",
      "/dns4/sgp-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu",
      "/dns4/nyc-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLueR4xBeUbY9WZ9xGUUxunbKWcrNFTDAadQJmocnWm",
      "/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64"
    ]
  }
})

AFTER (note that those nodes are gone):

window.ipfs = new IPFS({
            init: true,
            start: true,
            config: {
               Bootstrap: [
                  "/dns4/ams-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd",
                  "/dns4/lon-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLMeWqB7YGVLJN3pNLQpmmEk35v6wYtsMGLzSr5QBU3",
                  "/dns4/sfo-3.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM",
                  "/dns4/sgp-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu",
                  "/dns4/nyc-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLueR4xBeUbY9WZ9xGUUxunbKWcrNFTDAadQJmocnWm",
                  "/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64"
               ]
            }
         })

[daviddias]

This is no longer an issue in js-ipfs 0.25.3. Fixed with 5ec27a3

[rstormsf]

it's still the issue
@diasdavid

[sriharrsha]

I'm on 0.33.1

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

Any Help?

[sriharrsha]

This is no longer an issue in js-ipfs 0.25.3. Fixed with 5ec27a3

This is still an ongoing issue.

[sriharrsha]

it's still the issue
@diasdavid

Any Update?

[hushino]

same issue here with ipfs 0.33.1

[Juanperezc]

Rt

[hushino]

use this solve the problem

 Bootstrap: [
        "/dns4/ams-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd",
        "/dns4/lon-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLMeWqB7YGVLJN3pNLQpmmEk35v6wYtsMGLzSr5QBU3",
        "/dns4/nyc-1.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLueR4xBeUbY9WZ9xGUUxunbKWcrNFTDAadQJmocnWm",
        "/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64"
      ]

[tomnyson]

thank for problem

[AravDalwani]

Hi, I am getting similiar websocket error but with the localhost IP address. Can anyone please please help me out?
IPFS is not connecting because of this

JS-IPFS version: 0.47.0

[giraffekey]

I am getting that localhost error too, on version 0.48.1.

[zhgromov]

again this problem... how I can fix this?

[d4mr]

We are having the same problem. Any updates?

[zhgromov]

We are having the same problem. Any updates?

we cancel this lib and use "ipfs-core": "^0.2.0",

next,
initialize node from ipfs via window

    const node = window.IpfsCore.create({
      repo: "projectName",
      init: {
        emptyRepo: true,
        algorithm: "ed25519",
      },
    });
    node.then((i) => this.setState({nodeIPFS: i}))

after that, upload files to connected ipfs node from first code example

  const addToIpfs = async (file) => {
    const {path} = await node.add(file);

    if (path) {
      console.log(path);
      // await node.stop();
      // setSNode(false)
      return path
    }
  };

[d4mr]

@zhgromov thanks a ton, let me try this