Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websocket down? #1237

Closed
mitra42 opened this issue Feb 27, 2018 · 4 comments
Closed

Websocket down? #1237

mitra42 opened this issue Feb 27, 2018 · 4 comments

Comments

@mitra42
Copy link

mitra42 commented Feb 27, 2018

Has something changed, or is the websocket sync point moved/down ?

Since yesterday I've been seeing:
dweb_transport_ipfs_bundled.js:40529 WebSocket connection to 'wss://ws-star.discovery.libp2p.io/socket.io/?EIO=3&transport=websocket' failed: Error during WebSocket handshake: Unexpected response code: 502

Everything else seems good - e.g. connections to the http gateway at https://ipfs.io are working.

Version: ipfs 0.27.7
System: OSX (10.13.3 current)
Browsers: Firefox 58.0.2 & Chrome 64.0.3282.167 i.e. both current
My configuration is ...

{
"repo":"/tmp/dweb_ipfsv2700",
"config":{ 
    "Addresses": {
        "Swarm":["/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star"]
}},
"EXPERIMENTAL":{"pubsub":true}
}
@ghost
Copy link

ghost commented Feb 28, 2018

Sorry, dokku failed on us here, the ws-star container restarted and got a new internal IP, but nginx didn't get its vhost config updated.

@mitra42 could you confirm it's back?

@victorbjelkholm here's what I did: dokku nginx:build-config ws-star

@mitra42
Copy link
Author

mitra42 commented Feb 28, 2018

Thanks Lars - its back.

Lars - is setting something like this up here at Archive.org part of what David Dias asked you if you could help with ?

@victorb
Copy link
Member

victorb commented Feb 28, 2018

@lgierth thanks!

@mitra42 to avoid being blocked by experimental services being down in the future, you should run either https://github.com/libp2p/js-libp2p-websocket-star-rendezvous for websockets or https://github.com/libp2p/js-libp2p-webrtc-star for webrtc within your own network.

To get up and running, you should do the following:

  • Clone the repository
  • Pull down dependencies (yarn or npm install)
  • Run npm start for ws-star or npm run star-signal for webrtc-star
  • Then you can just use the IP + port of star-signal as a multiaddr in your node configuration, instead of the discovery.libp2p.io ones.

@victorb victorb closed this as completed Feb 28, 2018
@mitra42
Copy link
Author

mitra42 commented Feb 28, 2018

@victorbjelkholm - @diasdavid had a specific suggestion about what we needed to do at the Archive, and I don't think it was what you are suggesting above - and the sysadmin's couldn't follow what was being requested. He asked @lgierth to help but we haven't heard back.

MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this issue May 22, 2020
* chore: update ipfsd-ctl to latest version

Also uses the same ipfsd factory for all tests.

* chore: remove gh dep version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants