{"id":400,"date":"2016-10-18T11:58:07","date_gmt":"2016-10-18T11:58:07","guid":{"rendered":"http:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/?p=400"},"modified":"2016-10-18T11:58:07","modified_gmt":"2016-10-18T11:58:07","slug":"chrome-cant-connect-to-google-com-irony-overload-detected","status":"publish","type":"post","link":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/2016\/10\/18\/chrome-cant-connect-to-google-com-irony-overload-detected\/","title":{"rendered":"Chrome can&#8217;t connect to google.com &#8211; irony overload detected"},"content":{"rendered":"<p>An interesting problem started to pop up for Chrome users starting on Friday 14th &#8211; Chrome was unable to connect to any Google website. Other browsers were fine, but Chrome was having none of it.<\/p>\n<p>A recent update to Chrome seems to be favouring the use of Google&#8217;s new QUIC protocol to connect to their servers, rather than HTTP(S). At the moment QUIC is blocked at the campus firewall so this doesn&#8217;t work, but Chrome doesn&#8217;t seem to want to give up, and decides that if it can&#8217;t have QUIC then you&#8217;re getting nothing.<\/p>\n<p>At the moment the only way to fix things is to block the use of QUIC. Open a new Chrome tab, and enter the address:<\/p>\n<p><strong>chrome:\/\/flags\/#enable-quic<\/strong><\/p>\n<p>and change the popup menu from &#8216;<strong>Default<\/strong>&#8216; to &#8216;<strong>Disabled<\/strong>&#8216;. Chrome will then ask to restart and once that&#8217;s done all should be well again.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-401\" alt=\"Screenshot of Google Chrome QUIC settings\" src=\"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-content\/uploads\/sites\/66\/2016\/10\/Screen-Shot-2016-10-18-at-12.50.50.png\" width=\"994\" height=\"342\" srcset=\"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-content\/uploads\/sites\/66\/2016\/10\/Screen-Shot-2016-10-18-at-12.50.50.png 994w, https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-content\/uploads\/sites\/66\/2016\/10\/Screen-Shot-2016-10-18-at-12.50.50-300x103.png 300w, https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-content\/uploads\/sites\/66\/2016\/10\/Screen-Shot-2016-10-18-at-12.50.50-768x264.png 768w\" sizes=\"auto, (max-width: 994px) 100vw, 994px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Update &#8211; 19th Oct \u2013\u00a0<\/strong>Networks are aware of the issue and working to enable QUIC through the firewall. The issue has been replicated on a lot of Macs and also Windows 10 systems.<\/p>\n<p><strong>Update 2 &#8211; 19th Oct \u2013<\/strong> Even with the firewall allowing QUIC to pass through it seems that Chrome v54 &#8211; which started auto-deployment last week &#8211; has a bug which triggers this issue. There similar reports on the <a href=\"https:\/\/googlechromereleases.blogspot.co.uk\/2016\/10\/stable-channel-update-for-desktop.html\">Chrome releases blog<\/a>. We may have to wait for Google to fix this! Chrome v53 seems to behave properly &#8211; either using QUIC or else falling back to HTTPS as it should.<\/p>\n<p><strong>Update 3 &#8211; 21st Oct \u2013<\/strong> Chrome\u00a054.0.2840.71 has been released which appears to fix this problem! If you disabled QUIC I don&#8217;t see much to gain by re-enabling unless you&#8217;re feeling keen.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An interesting problem started to pop up for Chrome users starting on Friday 14th &#8211; Chrome was unable to connect to any Google website. Other browsers were fine, but Chrome was having none of it. A recent update to Chrome &hellip; <a href=\"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/2016\/10\/18\/chrome-cant-connect-to-google-com-irony-overload-detected\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":83,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-400","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pa93hP-6s","_links":{"self":[{"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/posts\/400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/users\/83"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/comments?post=400"}],"version-history":[{"count":0,"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/posts\/400\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/media?parent=400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/categories?post=400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.qub.ac.uk\/screenshotsfromtheedge\/wp-json\/wp\/v2\/tags?post=400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}