WARP gets an error "unable to connect" if AdGuard is already running

[Aydinv13]

AdGuard version

2.10

Browser version

No response

OS version

13.3.

What filters do you have enabled?

No response

What Stealth Mode options do you have enabled?

No response

Support ticket ID

No response

Issue Details

Steps to reproduce:

1. Install WARP
2. Run AdGuard
3. Try to to connect via WARP

Expected Behavior

WARP successfully connected

Actual Behavior

Unable to connect error

Screenshots

Screenshot

Additional Information

No response

[brknstrngz]

I ran into this as well. After digging through the debug logs of the Warp client, applying the following DNS rewrites (my only upstream DNS is a self-hosted instance of Adguard Home) solved this for me:

warp-svc to 127.0.2.2
warp-svc to 127.0.2.3
warp-svc to fd01:db8:1111::2
warp-svc to fd01:db8:1111::3

I wish I could remember why it was these particular 4 addresses, it has been a while back. Another workaround that I have not yet tried could be to add warp-svc to the network.extension.exclude.domains list in the advanced settings section.