Skip to content
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.

Error: Not connected #80

Open
mqklin opened this issue Feb 7, 2020 · 2 comments
Open

Error: Not connected #80

mqklin opened this issue Feb 7, 2020 · 2 comments

Comments

@mqklin
Copy link

mqklin commented Feb 7, 2020

We use 3box library, that uses ipfs, that uses this library.
We are getting lots of this error in our Sentry:

{code: -1, message: Not connected}

Could you please explain what can cause this error and how can we fix it?

@jacobheun
Copy link
Contributor

Do you have a stack trace for the error? What version of libp2p-websocket-star are you running?

The transport should only throw errors with message "Not connected" when it was not able to connect to the target server, which could mean the rendezvous server it is attempting to connect to is unavailable.

@mqklin
Copy link
Author

mqklin commented Feb 10, 2020

version "0.10.2"
No, I have only this error (we use Sentry).
Can this error be triggered because of internet provider restrictions? Can VPN fix this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants