Tested the issue using #60.0.3112.107 on OnePlus 3T 7.1.1 and was unable to reproduce the issue. Able to navigate to pages using Wifi in Chrome

@urmommasofat5: Could you please clear cache and browsing data of your browser and recheck the issue and update.

Thanks you!!

Two more questions:

Does this happen on one specific wifi network, or all of them?

If you're still seeing the issue, can you please post a net-internals log following the instructions at https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details ?

Cleared cache and data but still happens.
It happens to all WiFi networks

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like you're using Data Saver.  For some reason the Data Saver proxy ("compress.googlezip.net") is being mapped to "192.168.1.3" by your DNS server (Which is a local IP, rather than a real IP used by the Data Saver service).  When we try and connect to that IP, we get ERR_CONNECTION_RESET, and for some reason are no falling back to using a direct connection.

For now, I suggest disabling Data Saver (Should be near the bottom of settings).

The DNS address seems to be resolved correctly for compress.googlezip.net (216.58.204.140:80). I think "192.168.1.3" pointed out by mmenke@ in #7 is the source (aka local) socket address.

It's still a bit weird why we are not falling back to DIRECT connection. I see that in the list of the proxies. I will try to repro this to see if there is something wrong with the fallback mechanism.

Oops, you're correct.

Looking at the netlog, it seems that the transport layer connection attempt to compress.googlezip.net succeeded (or at least socket layer believed it succeeded). However, later when trying to fetch content over it, the socket reported ERR_CONNECTION_RESET. Could it be because we were using a stale socket?

mmenke: Are the stale sockets carried over when there is a connection change?

All of the sockets were fresh.  When there's a network change, we do flush the socket pool.

Problem solved! Thanks to mmenke for solving an 8 months problem! It was due to the data savings. Cheers guys!

OK, then ERR_CONNECTION_RESET is coming from the network after connection establishment. That's why we did not fall back to the next proxy.