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

No traffic goes through when Wireguard VPN is active #23

Open
zod076 opened this issue Nov 23, 2024 · 2 comments
Open

No traffic goes through when Wireguard VPN is active #23

zod076 opened this issue Nov 23, 2024 · 2 comments

Comments

@zod076
Copy link

zod076 commented Nov 23, 2024

Hi, I've followed the RethinkDNS guide on setting up Wireguard. I chose to Import the config. Under Advance, I pick 2 apps(browsers) to route through the VPN to test.

With the Wireguard VPN in active state and rdns mode set to recommended(dns+firewall), visiting any sites results in no response from server error message. Sometimes I get lookup taking too long error(dns).

I've tried stopping rdns, force closing the app, opening rdns and starting rdns again but to no avail.

When I disable and delete the Wireguard profile and just rely on dns+firewall everything works.

What could be happening ?

@zod076
Copy link
Author

zod076 commented Nov 23, 2024

Btw, if I use the same Wireguard config with the official Wireguard app on Android, it works.

@zod076 zod076 closed this as completed Dec 15, 2024
@ignoramous
Copy link
Contributor

What could be happening ?

Does your WireGuard config contain domain name for the Peer endpoint? If so, this is currently broken but fixed in the upcoming version v055o. You can opt to remove the domain name and use IP address instead.

Another reason could be that the WireGuard profile you're running is IPv6-only but the underlying network (wifi or mobile) is IPv4-only (or vice versa). This doesn't cause problems with official WireGuard app because it runs only ONE WireGuard tunnel at a time (unlike Rethink which can run multiple when in Advanced mode).

If so, see if switching WireGuard to Simple mode and fixes the issue you're seeing?

@ignoramous ignoramous reopened this Dec 15, 2024
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