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

Failed to connect: could not create p2p channel during connect: p2p dialer failed: could not dial p2p channel: could not ping peer: too few connections were built #467 #506

Closed
igsergor opened this issue Jan 27, 2024 · 4 comments
Labels
bug Something isn't working stale

Comments

@igsergor
Copy link

Describe the bug
A clear and concise description of what the bug is. - it is actual issue - please get it not closed

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Logs
Attach logs (app, node, supervisor) to the issue. Where to find the logs: https://github.com/mysteriumnetwork/mysterium-vpn-desktop#logs

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. Windows 10]
  • App Version [e.g. 4.1.0]

Additional context
Add any other context about the problem here.

@igsergor igsergor added the bug Something isn't working label Jan 27, 2024
@Kefpull
Copy link

Kefpull commented Feb 19, 2024

I've noticed this happens when trying to connect while using T-Mobile Home Internet (rather than my normal cable wifi), it might have something to do with your ISP if it's consistent.

@rinzler100
Copy link

I have this problem when on my ISP (Spectrum). Hopefully a workaround is created.

@rinzler100
Copy link

Updating info here, same error is thrown on multiple devices and multiple wallets (accounts), and happens on any ISP (Verizon, T-Mobile, Spectrum home internet, etc.).

Copy link

stale bot commented May 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Is this issue still relevant?

@stale stale bot added the stale label May 22, 2024
@stale stale bot closed this as completed May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

3 participants