AdguardTeam / AdguardForAndroid

Open bug tracker for Android version of AdGuard.
https://adguard.com/
1.32k stars 90 forks source link

"No connection" error in Google Play when manual proxy mode is used #8

Closed ameshkov closed 9 years ago

ameshkov commented 9 years ago

Linked forum thread: http://forum.adguard.com/showthread.php?6547-Version-2-0-60-problems-remain&p=58456#post58456

TPS commented 9 years ago

I actually had this happen last night! I rebooted & went on my way.… Do you think the log will still be any good? I'll send it in now, just in case.

Ticket #OKU-154-26345

ameshkov commented 9 years ago

Error line:

TCP id=567 Error processing request https://play.googleapis.com:443: java.net.ConnectException failed to connect to /64.233.185.95 (port 443): connect failed: ENETUNREACH (Network is unreachable)

Seems that there were some problems with net connection, so I don't think this is somehow caused by Adguard.

TPS commented 9 years ago

Play store was only app with problem. I could even get to GPlay on the browser, just not via app, but fixed on reboot.

ameshkov commented 9 years ago

For me it looks like GPlay problem very similar to Error 194 problem: https://productforums.google.com/forum/#!topic/play/hIIJ1nauNf4

They had some problems with connections caching.

TPS commented 9 years ago

Mine resolves on reboot, though.… The linked issue persists, & mine doesn't happen when AdGuard isn't running.

Update: I had this happen again, & played a hunch: I wiped all AG data from app settings, re-adjusted settings, & then updated all filters. Fixed this completely without reboot! I have a thought, because my DSL connection is flaky, that, when the connection blinked, the router poisoned (to route to internal webpage stating connection loss) some sort of internal AG DNS cache, which persists after the connection restores.

Revertron commented 9 years ago

Sooo, what we are doing? I've tested this back and forth and can't reproduce it at all.

ameshkov commented 9 years ago

Ok, let's close it.

I am pretty sure the problem was in Google Play and Google Play Services apps.