Open Eollone opened 1 month ago
@Eollone Hi! If you disable HTTPS filtering for QQ app in the App management tab, would the issue persist?
@Versty Hi,
Yes, the problem also remains after disable HTTPS filtering.
After further investigation, I discovered that enabling “Network - Proxy - Proxy server - Route UDP through SOCKS5” was causing the issue. This setting seems to render the addition of QQ to the "Low-level settings - QUIC bypass packages" ineffective, resulting in slow image loading in QQ.
Once I disabled “Route UDP through SOCKS5” and added QQ to the "QUIC bypass packages," QQ loaded normally.
However, I’m a bit puzzled because QQ has always been set to bypass the proxy (the “Route app through proxy” setting of QQ is turned off). Therefore, I would expect that enabling “Route UDP through SOCKS5” should not affect QQ's network traffic.
This is just a temporary solution, as it prevents other applications that require the proxy from routing UDP traffic properly.
Please answer the following questions for yourself before submitting an issue
AdGuard version
4.6.3
Environment
HTTPS filtering
Root access
Integration with AdGuard VPN
Routing mode
Local VPN
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Language-specific
No response
Other
No response
Which DNS server do you use?
DNS protection disabled
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Issue Details
Steps to reproduce:
Install AdGuard and QQ [1] normally.
Enable traffic routing for QQ through AdGuard.
When receiving images in QQ, the loading time is excessively long (over ten seconds).
Troubleshooting Completed:
Disabling all AdGuard features (including "Ad blocking," "Tracking protection," "Annoyance blocking," "DNS protection," "Firewall," and "Browsing Security") did not resolve the issue. The image loading speed only returned to normal when the "Route traffic through AdGuard" option in QQ was disabled.
Attempted to add QQ to the "QUIC bypass packages" in "Low-level settings," but the issue persisted.
Tested with Rethink [2] instead of AdGuard, and QQ's image loading was normal, suggesting that it is probably not a compatibility issue with QQ.
Expected Behavior
Images in QQ should load quickly and efficiently when using AdGuard.
Actual Behavior
Images in QQ take an excessively long time to load when using AdGuard to route the traffic.
Screenshots
No response
Additional Information
No response