socks5 proxy not working with Adguard 4.0

[terrytw]

Please answer the following questions for yourself before submitting an issue.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard version

4.0

Environment

- OS: Android 12
- Device: Xperia 5 II
- Firmware: Lastest

Root access

• Yes, I have it.

What filters do you have enabled?

AdGuard Base filter, AdGuard Mobile Ads filter

What Stealth Mode options do you have enabled?

No response

Issue Details

Steps to reproduce:

1. Setup any socks5 proxy
2. Connect to said proxy via Adguard
3. Try connecting to google.com

Expected Behavior

Smooth internet connection.

Actual Behavior

No internet connection.

Additional Information

No response

[sfionov]

@terrytw We have a fix for outbound proxies in "4.1 nightly 7", can you please check if helps you?

Note: Don't forget to export and save your settings before installing nightly version.

[sfionov]

UPD: Seems that nightly is not out yet, sorry. It will be available today or tomorrow.

[terrytw]

Sure, I will check it up and come back to you. Thanks for the response.

[Versty]

@terrytw The version should be available. Please check if this issue is fixed on your device.

[terrytw]

@Versty Dear Diana,

Thanks for the follow up, I just tested the 4.1 nightly 8, it seems that connection issue has been fixed.

However, the "check connection" button in socks5 proxy is still malfunctioning. When i clicked on the "check connection" button, sometimes it says "connection working" and sometimes it says "TCP connection failed". But in reality the connection is working.

[Versty]

@terrytw We would like to take a look at the logs from your device.

1. Enable debug logging:
   Settings -> General -> Advanced -> Logging level -> Debug

2. Reproduce the issue related to the button behaviour, then remember the exact time when it happened

3. Collect logs:
   Settings -> General -> Advanced -> Export logs and system info

4. Sent this file to devteam@adguard.com:

   • mention the 4812 number in the subject
   • specify the exact time when the issue occurred

[terrytw]

Dear Diana,

I have sent the logs via E-mail.

[Versty]

@terrytw Thanks!
We have received your logs and are currently examining them.

[sfionov]

@terrytw We have read your logs. Does you proxy support IPv6? Seems that IPv6 connection via proxy is successful but immediately resets. So it fails when IPv6 is connected faster than IPv4. I think that it is better to fix on proxy side, since this behavior (successful connect + reset) may lead to problems in other apps too.

[terrytw]

@sfionov Dear dev,

Unfortunately it is not the case you just described. Please refer to the following 2 pictures:

First one is taken with adguard and proxy enabled, second one is taken with adguard and proxy disabled. As you can see, IPv6 is not available at all.

On top of that, the proxy I have worked perfectly fine with Adguard 3.6.8.

One thing I would like to mention is that the problem only occurs with mobile network, not with wireless.

[ngorskikh]

@terrytw Hello! So are you using a local proxy (i.e. a proxy that is on the same machine as the client)? What software is it? I'd like to replicate your setup to get a better understanding.

[terrytw]

@ngorskikh Hi I am using shadowsocks-android from the play store (with v2ray-plugin and UDP fallback) at proxy only mode. UDP over socks5 also worked fine.

[Versty]

@terrytw We have found a root cause. Currently working on the fix, will be available as a part of CoreLibs v1.12.

[terrytw]

@Versty Thanks for the update, I really appreciate it!

Happy to know you guys find out the problem, great work as always!