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

AdGuard cannot filter the app if Automatic Proxy + Wireguard VPN are enabled #1298

Open
validatedev opened this issue Sep 18, 2023 · 11 comments

Comments

@validatedev
Copy link

AdGuard version

2.11.0.1292

Browser version

Google Chrome Version 117.0.5938.88, Arc Browser 1.8.1 (Chromium Engine Version 116.0.5845.187)

OS version

macOS Sonoma 14.0 RC1 (23A339)

What filters do you have enabled?

AdGuard Base filter, AdGuard Mobile Ads filter, AdGuard Turkish filter, AdGuard Annoyances filter, Adblock Warning Removal List, Online Malicious URL Blocklist, I don't care about cookies

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

In macOS Sonoma, if Automatic Proxy is enabled and VPN is enabled (I have tried with a Wireguard one, didn't test with other protocols), with a Chromium browser (tested with Arc and Chrome), Adguard test page says Adguard is not running even though Adguard browser extension says it is running. Network Extension mode works flawlessly in that case. Also, Automatic Proxy + VPN configuration works with Safari.

Expected Behavior

Adguard should filter ads.

Actual Behavior

Adguard is not filtering ads.

Screenshots

Video Recording 1:
Screen.Recording.2023-09-18.at.14.52.29.mov

Additional Information

No response

@validatedev
Copy link
Author

Also tested with Version 2.12.0.1379 beta, same issue.

@AlexandrPkhm
Copy link
Contributor

Hi @validatedev

Unfortunately, we have not been able to reproduce the problem. To troubleshoot it, we need to get the application logs. Could you please record them for us? Here's what we need you to do:

  1. Click AdGuard icon in the menu bar → Gear → Advanced → Logging → Logging level → Debug;
  2. Reproduce the issue and remember the exact time it happened;
  3. Menu → Advanced → Logging → Export Logs and System Info...;
  4. Send the archive to [email protected] and mention this issue number in the subject.

@validatedev
Copy link
Author

@AlexandrPkhm The logs are sent with title "About Issue #1298 in AdGuard For Mac Repo in GitHub".

@AlexandrPkhm
Copy link
Contributor

Hi @validatedev

We apologize for the delay. Could you please let us know if the problem persists with AdGuard for Mac 2.12.1? And if so, please let us know if disabling WireGuard VPN solves the problem.

@validatedev
Copy link
Author

Hi @AlexandrPkhm thanks for the answer. No worries for the delay :)

Unfortunately, still the same issue with 2.12.1.

WireGuard VPN not active + AdGuard Network Extension active -> AdGuard can filter
WireGuard VPN active + AdGuard Network Extension active -> AdGuard can filter
WireGuard VPN not active + AdGuard Automatic Proxy active -> AdGuard can filter
WireGuard VPN active + AdGuard Automatic Proxy active -> AdGuard cannot filter and in https://adguard.com/en/test.html it says (not running) also stated with screen recording.

@AlexandrPkhm
Copy link
Contributor

Hi @validatedev

In this particular case, it appears that your specific Wireguard VPN settings may be causing the problem. Please specify the following. Are you using a custom DNS server with your Wireguard client? Are you passing traffic from all IP addresses through a VPN tunnel, or only certain IP addresses?

@AlexandrPkhm
Copy link
Contributor

Hi @validatedev

Any news on the issue?

@validatedev
Copy link
Author

@AlexandrPkhm Sorry about the delay, had a hectic week :/ Will inform in 1-2 days.

@AlexandrPkhm
Copy link
Contributor

AlexandrPkhm commented Nov 8, 2023

Hi @validatedev

Could you please let us know if you were able to get the information needed to determine the root cause of the problem?

@validatedev
Copy link
Author

validatedev commented Nov 8, 2023

@AlexandrPkhm So sorry about the delay. Finally found a time to investigate.

Actually, my WireGuard config is a WARP (1.1.1.1) config which is generated via https://github.com/ViRb3/wgcf. Also, I added the NextDNS IPv6 addresses.

My config is simply like:

[Interface]
PrivateKey = <redacted>
Address = <redacted>/32
Address = <redacted>/128
DNS = <redacted>
DNS = <redacted>
MTU = 1280
[Peer]
PublicKey = <redacted>
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = <redacted>

As could be seen, I pass all traffic on WireGuard.

@adguard-bot adguard-bot assigned sfionov and unassigned AlexandrPkhm Nov 13, 2023
@validatedev
Copy link
Author

Any update? @sfionov @AlexandrPkhm

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

No branches or pull requests

5 participants