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
Comments
|
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: |
|
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 ? |
|
@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:
|
|
@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. |
* chore: update ipfsd-ctl to latest version Also uses the same ipfsd factory for all tests. * chore: remove gh dep version
mitra42 commentedFeb 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 ...
The text was updated successfully, but these errors were encountered: