Skip to content

Server unreachable on client activation on wireguard #1894

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

Open
prooshani opened this issue Oct 13, 2020 · 1 comment
Open

Server unreachable on client activation on wireguard #1894

prooshani opened this issue Oct 13, 2020 · 1 comment

Comments

@prooshani
Copy link

I have managed to build 3 different instances of Algo vpn on two different cloud systems.

  • 2 instances on Digital Ocean
  • 1 instance on GCE
    all 3 created using same config file.

Just one of them works correctly on wifi and none of them connects on cellular when using Wireguard profiles.

I can ping and ssh all of them and they are reachable.

one of them ( san fransesco droplet on Digital ocean) works fine on wifi and the other two (NY on Digital ocean and London on GCE) when the client try to connect using wireguard connection the server became unreachable and returns no ping and when the client deactivate the wireguard the ping became normal.

The funny point is that if I use vpn on my router and redirect my traffic the problem disappears and all servers connect smoothly.

I have checked and all droplets' firewalls are inactive.

I can't trace the problem.

@adhamnm
Copy link

adhamnm commented Oct 18, 2020

The same thing happened to me. I have 1 Algo instance on ec2 that's been up and running for the past month. I tried to connect to it from my mac and iphone using wireguard client but the connection is unreachable. This has been going on for the past week.

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