unable to access Gmail account via Chromium browser on Raspberry Pi

1,042 views
Skip to first unread message

Bill Stanard

unread,
Mar 23, 2017, 4:09:31 AM3/23/17
to Chromium-discuss
I'm setting up a summer program with RPi's and middle school kids, and I want then to each have a Gmail account to (a) enable them to use many of the Google goodies available, (b) to send and receive eMails, and (c) to allow them access to other sites such as MIT's App Inventor using their Gmail ID. Their Pi's will be running headless using Ethernet connections and VNC in the school computer lab.

Using Chromium, a student can set up a Gmail account with no problem.

Problem: the Chromium browser on the RPi throws the following error when attempting to access a Gmail account: 
This site can’t provide a secure connection
mail.google.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR


Is there another way to access Gmail (https://mail.google.com/mail/?tab=wm) on the Chromium browser?

I am using the latest Raspian build of Chromium (Chromium 56.0.2924.84 Built on Ubuntu 14.04, running on Raspbian 8.0 on a RPi 3 Model B) and I am running the Pi headless using RealVNC server on the Pi and RealVNC client on a Windows 7 laptop. I can reach the gMail account with no problem on the labtop, via Chrome. 

Primiano Tucci

unread,
Mar 23, 2017, 6:11:20 AM3/23/17
to bsta...@gmail.com, Chromium-discuss
Do you have NTP or any sort of timesync enabled?
One possibility is that the RPi's clock is in the past, and that will fail all SSL cert validations.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

Bill Stanard

unread,
Mar 23, 2017, 11:18:39 AM3/23/17
to Chromium-discuss
I do have NTP enabled, and my clock is spot on.

Bill Stanard

unread,
Mar 23, 2017, 12:36:25 PM3/23/17
to Chromium-discuss
I have just downloaded Iceweasel (Firefox) and was able to log in to my Gmail account perfectly. Go figure! Looks like the issue is some setting that I've messed up in Chromium...


On Thursday, March 23, 2017 at 3:09:31 AM UTC-5, Bill Stanard wrote:
Reply all
Reply to author
Forward
0 new messages