AdguardForWindows
AdguardForWindows copied to clipboard
AdguardTeam
Cloudflare WARP can not connect
AdGuard version
AdGuard for Windows 7.15.0 nightly 31 (4467)
Browser version
Chrome 119
OS version
Windows 11 22H3
What filters do you have enabled?
AdGuard Base filter, AdGuard Tracking Protection filter, AdGuard URL Tracking filter, AdGuard Social Media filter, AdGuard Annoyances filter, AdGuard DNS filter, Fanboy's Anti-Facebook List
What Stealth Mode options do you have enabled?
Hide your search queries, Strip URLs of tracking parameters, Remove X-client-Data header from HTTP request
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Make sure Adguard is enabled including DNS protection
- In my case, DNS in Adguard is set to my own NextDNS
- Changing DNS in Adguard to System Default doesn't make any difference
Actual Behavior
Can not connect to internet
Expected Behavior
Should be able to connect
Screenshots
Additional Information
Based on Adguard for Nightly changelog it is supposed to be fixed in https://github.com/AdguardTeam/AdguardForWindows/issues/4871 So it seems Nightly already has CoreLibs 1.13.68 but I'm still having this issue.
DNS protection says it all, cloudflare warp changes the dns to 1.1.1.1 and this causes conflict. The solution is to disable adguard's dns protection to connect to war
DNS protection says it all, cloudflare warp changes the dns to 1.1.1.1 and this causes conflict. The solution is to disable adguard's dns protection to connect to war
I'm aware of this solution. But looking at AdGuard nightly's changelog, it seems the AdGuard team is implementing internal changes to make sure the users don't have to manually disable DNS protection to make it work with Warp. I think Warp is widely used by many people now so an automatic solution by AdGuard would be better for those users. As I explained in my report, the nightly was supposed to fix it but it didn't.
Certainly buddy because I also got a little beaten to use Warp because of this problem
Hi @SeriousHoax
We apologize for the delayed response. The following issue should be fixed in AdGuard for Windows 7.16. Could you please try to update to the latest version and check if you are still experiencing this issue? Please let us know the results.
@SeriousHoax
Could you please let us know if there is any news on this issue?
@SeriousHoax
Could you please let us know if there is any news on this issue?
Hi! I checked last night on AdGuard Stable and the issue still remains. I see that there are some other opened issues regarding the same problem: https://github.com/AdguardTeam/AdguardForWindows/issues/5006 https://github.com/AdguardTeam/AdguardForWindows/issues/4987
@SeriousHoax
Could you please let us know if there is any news on this issue?
I used Adguard 7.16nightly 22 (4556) and I found that the problem persisted. I can't use cloudflare warp when I use Adguard, unless I turn Adguard's DNS protection off
related to https://github.com/AdguardTeam/AdguardForWindows/issues/5006. Please follow the related issue
I'm having same issues. Disabling DNS protection in Adguard makes Warp connect. Is there anyway we can add a DNS filter to 'unblock' the WARP? I'm using the latest version on Windows 11.
@bithack3r Yes, disabling the DNS protection can solve the issue. We looked for solutions, but unfortunately WARP automatically detects any DNS filtration and doesn't allow it to happen. We might find a way to "avoid" this for a while, but this cannot be a permanent solution - it will be broken again sooner or later due to WARP policy.
