I was unable to parse the log dump from the user as JSON file. But looking at the log-net-log.txt manually, it seems like QUIC has network idle timeout as the quic error throwd is QUIC_NETWORK_IDLE_TIMEOUT. Is that only happening on the first-time login? Also, could repro the issue and  provide net-internals per instructional link so that we could get a clean net internals to help investigation? That will be really helpful.
https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Yes, the issue is happening only during first-time login.

I've already referred to the link you've mentioned. It says:

----
Logging on startup

If the problem that you want to log happens very early and you cannot open chrome://net-internals first, you can add a command line argument to Chrome to start logging as early as possible:

--log-net-log=C:\some_path\some_file_name.txt
-----

So I added this flag in /etc/chrome_dev.conf.

Is there any other way to get the logs in this scenario?

The end of your net-log looks like:

{"phase":2,"source":{"id":802,"type":1},"time":"3885769","type":98},
{"phase":1,"source":{"id":802,"type":1},"time":"3885769","type":130},
{"params":{"alternative_service":"Uninitialized :0","original_url":"http://www.gstatic.com/","priority":"LOWEST","source_dependency":{"id":802,"type":1},"url":"http://www.gstatic.com/"},"phase":1,"souchronos@localhost /tmp $
chronos@localhost /tmp $

How did you generate this file, since it seems to have unix command prompts in it as well? In addition, many of the lines are truncated. If you can attache the full file, we will be able to parse it.

Sorry for the incomplete logs earlier, attaching fresh logs.

I am not able to generate a "complete" file which can be parsed as is. I was playing around with these logs using http://www.jsoneditoronline.org and I was able to parse it by replacing "," at the end with "]}"
Not sure if it helps.

Deleted: log-net-log 851 KB

log-net-log 851 KB View Download

I noticed there are some related bugs already

https://bugs.chromium.org/p/chromium/issues/detail?id=648694
https://bugs.chromium.org/p/chromium/issues/detail?id=647370

So just wanted to point out that:
1. I am also using ethernet (I don't have wlan functional yet).
2. I also need to select Ethernet on "Connect to network" screen to proceed.

This looks like the user has responded.  rch@, is it reasonable to ask you to look at the logs and say if you need more than what's here?

I updated Chrome browser on my windows machine today to v54.0.2840.59 m.
After clearing the cookies and cached data, I face this issue when trying to access google hosted sites eg. google.com, chromium.org (This site can't be reached, ERR_QUIC_PROTOCOL_ERROR). I am able to bypass the issue by disabling quic (chrome://flags/#enable-quic).

I can see that another bug has been reported for this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=657050

Attaching net-internals-log from Windows.

Deleted: net-internals-log.json 323 KB

net-internals-log.json 323 KB View Download

I believe this issue is fixed in 54.0.2840.71 which was released today. If you upgrade to it, does the problem persist? Also, can you confirm if you're behind a Palo Alto networks firewall?

Thanks Ryan. I updated Chrome browser on Windows to v54.0.2840.71 and I don't see this issue anymore. I suppose this commit fixes the issue.
https://chromium.googlesource.com/chromium/src/+/ef8417b1baf6251d9e47fc8b7eb84ffb34e67272

I need some more time to verify the same of Chromium OS.

Glad to hear it!

Chromium OS login is also working fine.

However, this issue "OOBE network connection no longer proceeds automatically when ethernet is available" is still present.
https://bugs.chromium.org/p/chromium/issues/detail?id=648694
https://bugs.chromium.org/p/chromium/issues/detail?id=647370

And yes, I got to know that we use Palo Alto Networks firewall.

sumit.agr: Thanks for verifying! Is this OOBE issue specific to QUIC?

Jana, I am not sure I understand your comment.

There are two issues here:

1. First-time login failure (during OOBE) with ERR_QUIC_PROTOCOL_ERROR. This issue (which was specific to QUIC) seems to be resolved now with https://chromium.googlesource.com/chromium/src/+/ef8417b1baf6251d9e47fc8b7eb84ffb34e67272.

2. OOBE network connection no longer proceeds automatically when ethernet is available. This doesn't seem to be related to QUIC I guess and is being tracked here https://bugs.chromium.org/p/chromium/issues/detail?id=648694