For those experiencing this issue, disable the following setting in chrome://flags/ :
Experimental QUIC protocol Mac, Windows, Linux, Chrome OS, Android
Enable experimental QUIC protocol support. #enable-quic
I had the same problem this morning. Disabling QUIC solved it.
Disabling QIUC as parent links to unbroke things for me.
Funnily I switched to Microsoft Edge for a short while, but have once again realized why its unusable. After about 1-2 minutes using it, the entire browser became unresponsive for about 60 seconds. Afterwards I couldnt press sign-in on YouTube because an invisible IFrame from the OneNote Web Clipper Extension was overlaying it. Nobody seems to be testing those either :)
The only software where you can tell that they dogfood it is Visual Studio. Every change makes sense, is useful, user friendly and corresponds to problems I have met.
The other software that you would assume they dogfood but it doesn't show is Windows 10...
Also there are lots of use cases that they never bothered fixing or improving, which show they don't really use it. Like non resizable windows in excel (eg function wizard). Linking a powerpoint deck to an excel model (no good solution now). No way to do placeholders within a textbox in powerpoint (like you can in word). VBA not having evolved in nearly 20 years. You don't see this sort of "I don't give a shit" attitude with Visual Studio.
I am sure someone in the finance or marketing department at Microsoft uses office and is as frustrated as every other power user. But the developers in the office team clearly do not use their own product. If there are still any dev in the office team. The only changes I see from version to version are purely cosmetic.
Not to mention that the action of the Ribbon is kind of seizure inducing as the entire thing is in constant change as various objects are selected thereby unhiding specialized menus.
I've taken to minimizing the entire Ribbon so I don't have to see it, requiring me to re-learn and re-memorize the multi-key keyboard shortcuts since they are different than the 2003 version.
If I could kill the Ribbon with fire, I would.
This looks like an implementation error, either client or server-side.
For me what worked was removing Google's DNS server 220.127.116.11 from my network settings and voila; it worked.
I find it odd that QUIC is enabled by default when it apparently has poor fallback capabilities to "non-QUIC" mode.
So it is not only on Mac OS X
Edit: And it started working again :)
For some reason, even disabling it did not help.
Our workaround, was to use the old system browser for authentication and then switch to using chrome after being authenticated.
There's no hardware cause, it appears to be a minor chrome update combined with a QUIC server-side update (unconfirmed) that caused issues. As soon as Chrome auto-updates to the next minor release, things appear better (but not fully fixed).
It's entirely in the browser <-> Google server-side, ISPs have nothing to do with this.
> Google has not broken anything, Dutch providers have.
Based on what evidence, exactly? Aside from a grand scheme of evil world domination by Dutch ISPs, what exactly would their motive be for a coordinated action like this one which seems to only hurt Google properties and only over QUIC? Aside from a court order or responding to some kind of attack, I can't find a single compelling reason for ISPs to do this (and the fact that it's illegal by law and the fines are pretty big) unless they have a desire to flood their help desks.
Anybody seen anything like that? Is it possible that a corrupted packet could appear as a self-signed certificate? Did some MITM screw up?
Every time you connect a new device, you get a start page with the "welcome to your BT broadband" or whatever stupid thing they want. This screwed me for a few hours when I bought an Xbox One and most of the images wouldn't load. Had to open the browser, acknowledge the f*cking page and go on with my life.
Looking for a new router now...