chromium-browser youtube fails

[desktoppi]

Just did dist-upgrade to new versions of Raspian on my Pi 3. I started with fresh NOOBS and did upgrade. Chromium-browser now at V56.0.2924.84. When I try to start youtube it refuses to start and gives error: ERR_SSL_PROTOCOL_ERROR. Other google apps like gmail that use SSL do work okay. Also, this forum uses https: and that working fine, so the issue seems to be with chromium-browser

I was having other less serious errors on you-tube with chromium-browser V51 before the update. In my previous post on that I MISTAKENLY mentioned that I was running V56 on Ubuntu 16.04 (64bit) with no errors. In fact, I was running V55.0.2883.87, which is in fact still running fine. I mention that other post just in case someone was misled by that mistake.

[holt]

I have the exact same chromium-browser problem: version 51 worked fine, but now 56.0.2924.84-0ubuntu0.14.04.1.1000 (arising suddenly this week from "apt-get upgrade") fails with most all Google web sites, with this error messages:

This site can't provide a secure connection
www.google.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Which renders the Chromium browser nearly useless for many. Any idea how I can debug this? FYI the clock is set correctly on this RPi3 unit, with Timezone: America/New_York. Multiple reboots do not help. In conclusion, essentially all other web sites appear, but not most Google sites:

https://gmail.com
https://youtube.com
https://plus.google.com
https://hangouts.google.com

Conversely the site http://blog.google appears in part, but its images (arising from other Google properties, like storage.googleapis.com) do not load. Briefly https://google.com actually worked for a few short minutes about an hour ago, and I suspected that was b/c I changed the Timezone from America/New_York to Europe/London and back -- but then I was unable to reproduce this -- so this was very likely a complete fluke (only google.com worked during those brief minutes, not other Google web sites!)

We're talking about this on OLPC's server-devel mailing list, but don't have any real answers yet :/ Here's the thread:

http://lists.laptop.org/pipermail/serve ... 08083.html

Any other ideas we can try?

[Spillanepp]

I don't know if it is a permanent fix or not, but this worked for me:

1) in the address bar type: chrome://flags
2) Go down to the setting: "Maximum TLS version enabled"
3) change it from "default" to "TLS 1.2"

Hope this helps.
Patrick

[spacemanvic]

After a 3 hour phone call with Google support for Education, I've run into the same issue on certain WIndows 7 computers. The problem is with this release of Chrome 56. Ive tested beta (57) as well as alpha Chrome Canary (58). The problem will persist in 57, but is fixed in version 58. There is a glitch in Chrome 56/57 which I thought only effected Windows PCs. But after playing with my Raspberry Pi3 tonight, I discovered the issue exists here as well. In windows, the "fix" was for now, use a different browser or use a Chromebook. In Raspberry Pi land, we have to revert to an older version of Chromium. Not the most eloquent patch, but it gets the job done.

[holt]

Thank you so much Patrick for the interim fix. And spacemanvic for the assurance this will be fixed more methodically in coming months. These Raspbian forums are very supportive which is incredibly reassuring!

I'd love a more full explanation later as to how this keeps happening, if such insight arises later: why is a "Google product" (I'm assuming chromium-browser is tightly based on Chrome) repeatedly blocking essentially all Google sites in recent years, across many different OS's?

(It would appear thousands of Raspbian users will be very severely affected in coming weeks by this forced upgrade to an often-broken chromium-browser 56, tarnishing Raspbian unnecessarily, SAD!)

[Heater]

holt,

Not SAD at all.

What do you want, stick with old versions of software for a long time for fear of breaking things (The Debian approach) or be a bit more adventurous with new versions and risk the occasional breakage?

[lightstrike]

Hit the same issue on Ubuntu 16.04 (not on a Raspberry Pi) - Patrick's workaround did the trick, thanks

[pumatrax]

thanks Patrick, it worked for me as well. When I first discovered it my only desperate action was to rebuild the RPi. Its been working and of course what did I do?!? update the RPi again and boom same problem with Chromium.


I am glad google is my friend and I found this post. Thanks again!

[holt]

Indeed Patrick's workaround & spacemanvic's context above above saved us

Not sure when the Raspbian team will issue an official fix, mitigating the damage?

Root Cause Analysis: any suggestions on how to inform the Chromium team itself, so this repeat pattern & dramatic failure does not happen again?

[DavidS]

Thankyou for the temp fix for one of the problems.

Now does anyone know a fix for the current Chromium erroneously reporting HTTP 403 forbidden errors on pages that are verifiable as accessible?

[holt]

Hi David,

> current Chromium erroneously reporting HTTP 403 forbidden errors on pages that are verifiable as accessible?

What are example public URL(s), so that others may reproduce this?

[DavidS]

Hi David,

> current Chromium erroneously reporting HTTP 403 forbidden errors on pages that are verifiable as accessible?

What are example public URL(s), so that others may reproduce this?

Often times on http://distro.ibiblio.org/ in random timing random directories, this is where I notice it the most.

[ghostinthepi]

Thanks Patrick!

[cjan]

chromium-56, h264ify & H/W both enabled. youtube always frozen but not every time.
restart chromium can not solved the problem, need to reboot system.
ps. frozen circle running but video stream still downloading.

[Heater]

I got ERR_SSL_PROTOCOL_ERROR when visiting this forum earlier today with Chrome 56.0.2924.87 (64-bit).

Running on a Windows 10 machine!

The error went away after a few reloads.

[desktoppi]

I don't know if it is a permanent fix or not, but this worked for me:

1) in the address bar type: chrome://flags
2) Go down to the setting: "Maximum TLS version enabled"
3) change it from "default" to "TLS 1.2"

Hope this helps.
Patrick

This worked for my Raspberry Pi 3. Thank you.

[DavidS]

I got ERR_SSL_PROTOCOL_ERROR when visiting this forum earlier today with Chrome 56.0.2924.87 (64-bit).

Running on a Windows 10 machine!

The error went away after a few reloads.

Anything WinNT is suspect, though in this case it may be Chrome.