+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: Chromium on Pinebook Pro blocked by Google: "This browser or app may not be secure" (/showthread.php?tid=9325)
Chromium on Pinebook Pro blocked by Google: "This browser or app may not be secure" - lowry - 03-01-2020
Whatever I do, I can not login to my Google Account with Chromium on Pinebook Pro.
"Less secure apps" is on.
Firefox works so far.
RE: Chromium on Pinebook Pro: "This browser or app may not be secure" - jiyong - 03-04-2020
(03-01-2020, 02:28 PM)lowry Wrote: Whatever I do, I can not login with chromium on Pinebook Pro.
"Less secure apps" is on.
Firefox works so far.
I don't understand what you are doing.
Are you accessing a website that blocks you when you use Chromium?
RE: Chromium on Pinebook Pro: "This browser or app may not be secure" - lowry - 03-04-2020
(03-04-2020, 06:21 AM)jiyong Wrote:(03-01-2020, 02:28 PM)lowry Wrote: Whatever I do, I can not login with chromium on Pinebook Pro.
"Less secure apps" is on.
Firefox works so far.
I don't understand what you are doing.
Are you accessing a website that blocks you when you use Chromium?
Indeed. I can't login to Google Account with Chromium on Pinebook Pro.
RE: Chromium on Pinebook Pro: "This browser or app may not be secure" - jiyong - 03-05-2020
Ok, do you start Chromium from the panel (at the bottom), or through the menu?
Chromium starting from the panel spoofs the user-agent.
You can try to alter it to spoof a newer version (right click > properties).
Did you try to update Chromium with the package manager?
If all else fails, you can try to install a newer version with snap.
Jamie Phillips has a video where he explains how to do it.
https://www.youtube.com/watch?v=5STcNkylTAg
RE: Chromium on Pinebook Pro blocked by Google: "This browser or app may not be secure" - Eight Bit - 03-05-2020
I had the same happen, but it seemed it happened when I started Chromium before the network connection was established. When I quit Chromium, then reconnect the WiFi and restart Chromium it worked.