Adguard doesn't work with any proxy

[androidacy-user]

Issue Details

• AdGuard version:
  • 3.6.6 -> 4.0 nightly 31
• Filtering mode:
  • both auto proxy and vpn
• Device:
  • OnePlus 8t
• Operating system and version:
  • Android 11
• Root access:
  • yes, magisk

Expected Behavior

Proxy works as it does in all other clients

Actual Behavior

Proxy can't connect. Tested with NordVPN, windscribe, a self hosted one. All just say can't connect.

Screenshots

Screenshot:

Additional Information

[Chinaski1]

Hello!

So the issue started to reproduce after switching from the release to the Nighty version?

To troubleshoot this issue, we need to get additional logs.

Here's what we need you to do:

1. Collect the debug log as it's explained here;
2. Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
3. Send log files to devteam@adguard.com. Mention the Github issue number and the exact time when the issue was reproduced.

[androidacy-user]

Hello!

So the issue started to reproduce after switching from the release to the Nighty version?

To troubleshoot this issue, we need to get additional logs.

Here's what we need you to do:

1. Collect the debug log as it's explained here;
2. Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;
3. Send log files to devteam@adguard.com. Mention the Github issue number and the exact time when the issue was reproduced.

My apologies, what I meant is it doesn't work with any of those versions.

[Chinaski1]

@androidacybot

Can you provide the log files, please?

[Chinaski1]

Any updates?

[androidacy-user]

adguard_logs_4.0.73_0303_003018.zip Apologize for the delay - been really busy recently, but here's the logs. Issue was reproduced around a minute before logs end.

[Chinaski1]

Thank you for the information provided

I will let you know as soon as we have any recommendation about issue.

[sfionov]

@androidacybot

Hello! Sorry, I can't find exact time you did the test in the log. It contains only one IPv4 connection at the end of log.

How did you test proxy? If it is tested from UI, can you please write the log when protection is off?

[androidacy-user]

@androidacybot

Hello! Sorry, I can't find exact time you did the test in the log. It contains only one IPv4 connection at the end of log.

How did you test proxy? If it is tested from UI, can you please write the log when protection is off?

I narrowed it down in the end:

It only won't work with a DNS address. Ie, proxy.example.com will say unable to connect but 127.0.1.1 will work fine (with socks5, and even then sometimes Adguard won't connect when others will)

[maxikuzmin]

@androidacybot for now, we are looking into the problem

[maxikuzmin]

@androidacybot sorry for the wait. There is not enough information in your logs

To troubleshoot this issue, we need to get additional logs.

Here's what we need you to do:

• Collect the debug log as it's explained here;

• Remember the exact time when the issue was reproduced. We will need it to find the corresponding records in the log file;

• Additionally, capture the system bug report after reproducing the issue. Here's the instruction;

• Send both files to devteam@adguard.com. Mention the Github issue number and the exact time when the issue was reproduced.

[maxikuzmin]

@androidacy-user ping