| View previous topic :: View next topic |
| Author |
Message |
engineermdr
Apprentice
Joined: 08 Nov 2003
Posts: 295
Location: Altoona, WI, USA
|
 Posted: Wed Feb 10, 2016 4:22 pm Post subject: [SOLVED] Can't connect to Google sites with Chromium |
 |
|
I am suddenly unable to access any Google related sites, or signing in, with Chromium. I always get a page:
| Code: | SSL connection error
ERR_SSL_PROTOCOL_ERROR
Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. |
I can access any other SSL sites just fine. I can also access Google as expected using a different browser. Midori, in my case. I've tried rebuilding openssl, since I noticed it upgraded to 1.0.2f-r1 one day, and then downgraded to 1.0.2f the next day. I also tried rebuilding chromium. I even created a new user with an empty home directory and have the same problem, just to eliminate any cached data being the issue. I can access Google with Chrome on my Windows laptop. And I have found no similar issues in the forums or in bugs.
I'm kind of stuck as to what else to try or what's going on here. Any suggestions would be appreciated.
Last edited by engineermdr on Thu Feb 11, 2016 2:33 pm; edited 1 time in total |
|
| Back to top |
|
 |
sneakin
n00b
Joined: 26 Jun 2004
Posts: 4
|
| Posted: Wed Feb 10, 2016 11:02 pm Post subject: not alone |
|
|
Dealing with this too, except ninja crashes when I try to rebuild chromium.
_________________
sneakin |@t| semanticgap.com |
|
| Back to top |
|
|
engineermdr
Apprentice
Joined: 08 Nov 2003
Posts: 295
Location: Altoona, WI, USA
|
| Posted: Thu Feb 11, 2016 2:42 am Post subject: |
|
|
| Perhaps an important detail is that I am still running chromium-43, the last place widevine works so I can continue to watch Netflix. But from the ebuilds, it appears chromium uses a built-in ssl implementation. |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2575
Location: Here and Away Again
|
| Posted: Thu Feb 11, 2016 12:56 pm Post subject: ><)))°€ |
|
|
Which version of dev-libs/nss do you have installed?
I had this, or a very similar issue with QupZilla using QtWebEngine, which is sort of like using Chromium, but not, and while I found some old Chromium issues like this, they were quite old indeed and/or somehow different.
The issue was gone after I went from nss-3.21-r2 down to nss-3.20.1 which probably doesn't still explain the failure, since a QtWebEngine developer mentioned they were not having issues with nss-3.21-r2...
I haven't looked into it more than that, but I figured it's worth a shot, and interesting to see if it works for you, too.
_________________
Kindest of regardses. |
|
| Back to top |
|
|
engineermdr
Apprentice
Joined: 08 Nov 2003
Posts: 295
Location: Altoona, WI, USA
|
| Posted: Thu Feb 11, 2016 2:32 pm Post subject: |
|
|
Yes, downgrading to nss-3.20.1did the trick. Thank you so much.
Time to push getting widevine working in newer releases: bug547630 - www-client/chromium-44.0.2376.0 Fails to Compile with +widevine |
|
| Back to top |
|
|
Fog_Watch
Apprentice
Joined: 24 Jul 2006
Posts: 267
Location: Utility Muffin Research Kitchen
|
| Posted: Tue Mar 22, 2016 9:59 am Post subject: |
|
|
| Thanks Chiitoo |
|
| Back to top |
|
|
diablo465
Apprentice
Joined: 10 Sep 2013
Posts: 194
|
| Posted: Thu Mar 31, 2016 10:19 am Post subject: |
|
|
I had exactly the same issue just now.
What I resolve the problem is to make a recent update to chrome.
notice that you need to do a emerge --sync immediately before emerge google-chrome as ebuild for google-chrome updates very quickly. |
|
| Back to top |
|
|
|
Desktop Environments
