-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Wireguard does not connect to Algo server from my IP #1850
Comments
What kind of phone are you using (Android or iPhone)? What is this other VPN? Does it require an app that might be interfering with the WireGuard app? If so, can you uninstall it and try WireGuard again? Can you connect to your AlgoVPN from a different client (like a Mac or PC)? |
|
Could your country be blocking WireGuard, as mentioned in #1588? |
I'm not sure because I have access to the other VPS, which someone else installed Algo on it. I don't have SSH access to that VPS, and its provider is not Hetzner or DigitalOcean, but the same instruction installs it. |
I don't know a good way to test for country-level blocking. Perhaps the blocking also depends on where the server is located. |
Describe the bug
I deployed Algo on Hetzner and DigitalOcean servers by its GitHub instruction without any errors, but I can't connect to my Algo server using WireGuard. SSH Tunneling and socks proxy works, and everything looks fine. When I connect to another VPN first, I can connect to the Algo server by WireGuard! How can I find the problem?
When I'm trying to connect on my phone, the log is:
And
wg show
shows no connection to the server. The weird part is that it works when I connect to another VPN first!I used Ubuntu 20.04 on my server, and I chose the following option during the installation:
To Reproduce
It's not reproducible because, as I said, I could connect to my Algo server if I was connected to another VPN first. I used different ISPs, but it didn't help. I can give you more logs or information if you ask.
The text was updated successfully, but these errors were encountered: