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

Update reference to wss0.bootstrap.libp2p.io to be node0.preload.ipfs.io #268

Closed
klueq opened this issue Oct 28, 2018 · 3 comments
Closed
Labels
exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P3 Low: Not priority right now status/ready Ready to be worked

Comments

@klueq
Copy link

klueq commented Oct 28, 2018

I'm getting "invalid cert" errors in the console:

WebSocket connection to 'wss://wss0.bootstrap.libp2p.io/' failed:
Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID

https://websocket.org/echo.html also says that wss0.bootstrap.libp2p.io doesn't work.

However js-ipfs connects to the ipfs network and can download a file.

See a small demo at https://klueq.github.io

@jacobheun
Copy link
Contributor

Yes, it's been changed to wss://node0.preload.ipfs.io. Both point to the same node, however the certificate is only valid for node0.preload.ipfs.io, so the connection fails for the old url.

The reference to this needs to get removed from the repo, I think it's only in the browser example at the moment.

@jacobheun jacobheun changed the title wss0.bootstrap.libp2p.io is dead? Update reference to wss0.bootstrap.libp2p.io to be node0.preload.ipfs.io Oct 30, 2018
@jacobheun jacobheun added kind/bug A bug in existing code (including security flaws) help wanted Seeking public contribution on this issue exp/novice Someone with a little familiarity can pick up status/ready Ready to be worked P3 Low: Not priority right now labels Oct 30, 2018
@sriharrsha
Copy link

I'm on 0.33.1

error

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

Any Help?

@achingbrain
Copy link
Member

Closed as complete, please open a new issue if the problem persists.

maschad pushed a commit to maschad/js-libp2p that referenced this issue Jun 21, 2023
Bumps [it-pipe](https://github.com/alanshaw/it-pipe) from 2.0.5 to 3.0.1.
- [Release notes](https://github.com/alanshaw/it-pipe/releases)
- [Changelog](https://github.com/alanshaw/it-pipe/blob/master/CHANGELOG.md)
- [Commits](alanshaw/it-pipe@v2.0.5...v3.0.1)

---
updated-dependencies:
- dependency-name: it-pipe
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
maschad pushed a commit to maschad/js-libp2p that referenced this issue Jun 21, 2023
## [7.1.6](libp2p/js-libp2p-mplex@v7.1.5...v7.1.6) (2023-04-13)

### Dependencies

* **dev:** bump it-all from 2.0.1 to 3.0.1 ([libp2p#260](libp2p/js-libp2p-mplex#260)) ([c63ed58](libp2p/js-libp2p-mplex@c63ed58))
* **dev:** bump it-foreach from 1.0.1 to 2.0.2 ([libp2p#265](libp2p/js-libp2p-mplex#265)) ([76d27a4](libp2p/js-libp2p-mplex@76d27a4))
* **dev:** bump it-pipe from 2.0.5 to 3.0.1 ([libp2p#268](libp2p/js-libp2p-mplex#268)) ([bd37717](libp2p/js-libp2p-mplex@bd37717))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P3 Low: Not priority right now status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

4 participants