New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AdGuard blocks Internet connection #2842
Comments
@Chinaski1 "record everything"-level logs are required to troubleshoot |
Same problem : 1557976 Logs in NCloud And another one: 2240216 Logs in NCloud |
When switching from 4G to Wi / Fi, the Internet connection is lost User ID1889438 Logs in NCloud Your EnvironmentAdguard version: 3.1.0 |
One more user @ev_klzn |
Same issue for user 2240216. |
Another one user: 1254045 |
Also this one:
|
@Chinaski1 @TheHasagi to figure out what's wrong, we need to get the logcat log: It needs to be exported right after the issue is reproduced. |
Another report here - 2045896
And here - 1562409
|
We cannot reproduce this even on the same test devices. Here's what we need to troubleshoot:
|
it happens to me too, adguard_logs_3.2.95_1407_183159.zip the time it happened should be around 18:25: I restarted AG and connection was restored I'm running latest nightly on local proxy (root) with cloudflare dns (regular) |
what are all these `TLS connection is not HTTPS, adding 'com.facebook.katana#157.240.20.15:443#graph.facebook.com' to exceptions TLS connection is not HTTPS, adding 'com.facebook.katana#157.240.20.35:443#b-api.facebook.com' to exceptions TLS connection is not HTTPS, adding 'com.facebook.katana#157.240.20.35:443#b-graph.facebook.com' to exceptions TLS connection is not HTTPS, adding 'com.facebook.katana#157.240.20.15:443#api.facebook.com' to exceptions TLS connection may not be filtered because CA cert is not recognized by application, adding 'com.facebook.katana#157.240.20.10:443#edge-mqtt.facebook.com' to exceptions TLS connection is not HTTPS, adding 'com.instagram.android#157.240.20.63:443#i.instagram.com' to exceptions TLS connection may not be filtered because CA cert is not recognized by application, adding 'com.instagram.android#157.240.20.19:443#connect.facebook.net' to exceptions` should I do something about them? |
Progress update: 2228088 reports that the issue cannot be reproduced when his phone is connected to a PC. Asked for clean logcat logs, just for the case. 2240216, 1889438, 1254045, 2045896, 1562409: logs requested. Waiting for response. |
Find a logcat here (two instances collected in a different time): 2228088 |
One more user with this issue: 2075818. Requested logcats, waiting for reply. |
We have logcat from 1889438 |
@AdguardTeam/support-team guys, next time please request this instead of logcat. It contains all the necessary information + logcat. Besides that, we'll need to get AdGuard logs. Also, we'll need to know the time when the issue happened. Template: To troubleshoot this issue, we need to get the additional logs. When the issue happens again, please do the following:
|
Root is different. Most likely, AdGuard was killed by Android.
Nope, these are okay. |
Too late to record the logcat:( Please ask the user to do this: Considering that capturing Android bug report is not as complicated and does not require connecting to a computer, it'd be much easier to collect the necessary information. |
This one looks very relevant actually:
|
I didn't say that AG was killed, but my internet connection did, |
User ID: 2580549 |
User ID: 2595086 |
After all, at another one deep study of the problem, we noticed unusual network behavior that told us where the possible bug has been hidden. |
User 2669879 reports that the problem has not gone away. They are running AdGuard 3.4 beta 1. |
Got the situation from User 2669879, sent an email. |
I still have this error sometimes... |
Internet blocking issue still present on 3.4 stable. Yes, it's less prevalent compared to 3.3 but it's definitely not fixed. Also, It's not actually related to switching connections between wifi/LTE because many time it blocks internet access even in same WiFi connection, it's like internet was working a minute ago now no application can connect to internet unless I go to Adguard manually, and disable protection and re-enable it. (quick setting widget turn off/on also don't work to gain internet access back) I'm on POCO F1 but with custom ROM Android 10, so it's not like MIUI is shutting down adguard. But issue stays. (Same issue was there in stock MIUI Android 10 as well, same setup as described above) It's kind of random on daily basis but mostly happens after using device that has been in ideal for some time. Also, it doesn't happen right after waking up ideal device as internet works for sometime and then suddenly nothing connects ! So, manual reconnect is required to get Internet access back as described initially. Don't know what kind of logs you'll need for this so let know. |
@jineshpatel30 Your description is the same with me. I notice that the issue is not happened when using mobile data, it's seems only happen on wifi network. |
I'm on WiFi for like 99% of time, so what you're saying is highly probable but I can't confirm. |
@jineshpatel30 ok. Hope this issue is fix. |
Hey can you check whether internet blocking issue continues for you if you use "Proxy Blocking" method instead of VPN. (Auto proxy won't work without root but you can still setup manual proxy) Adguard will guide you through steps. I have an Interesting theory through my experiment yesterday. |
@jineshpatel30 I am checking now. |
I tried pause & resume few days back but some time that also doesn't work :( |
@jineshpatel30 is there any recommended proxy server? |
I don't think so, It's local proxy so there's nothing like different proxy server. Tough, I think Manual Proxy doesn't work with mobile data, You'll need WiFi for manual proxy setup. For me it was auto configured since I have root but here's manual setup guide. |
When the user switching from Wi/Fi to LTE internet connection is lost.
Need relaunch protection to reconnect.
"pref.vpn.disable.reconfigure" : true
"pref.vpn.disable.pause" : true
User ID
2228088
Logs
Your environment
The text was updated successfully, but these errors were encountered: