My Acer Chromebook constantly gives this error message despite having changed my password and performed a powerwash. What else can I do?
OK I’ve got one process that might help.
Do a Chrome Sync Reset from another browser.
Go to your Chrome Sync page https://www.google.com/settings/chrome/sync(logged in with the corresponding Google account).
Click Reset Sync at the bottom of the page.
On the Chromebook, try logging in again.
If this didn’t work you might need to troubleshoot with a Chrome Agent.
Are you using PIA vpn extension? Mine does this everytime I turn off my pixelbook with extension still running and sign in again.
Just a thought, but is the Chromebook’s time and date set correctly?
This just happened to me. I had to do a powerwash to finally fix it
Check timezones and system time. Can’t be too far off!
Mine was giving me this message constantly until I opened the “new sign in from device email in gmail and clicked the I trust this device option. Been working fine since 
I was getting that. I was on Beta channel but just went back to Stable. No more issues.
This happened to me and it was caused by the pia chrome extension. As soon as I would add that after a power wash this would come back.
I’ve seen this where a profile was synced from a newer version of Chrome OS when logging into older devices that didn’t support that particular version.
Do you have a sync password set up?
Are you running a VPN extension? If so, set it up to bypass, exclude, ignore, etc. www.googleapis.com
I had the same issue and this worked for me, thanks!
This! I have the same issue with nord VPN, may be some form of proxy error when verifying identity.
I use Hoxx VPN and have signed out of the Chromebook after disabling the VPN, however the same message pops up upon signing back in.
@reichstein you beat me by a minute in replying…I have quite some confidence that this is the issue.
Time and date are correct.
Beauty of a Chromebook is there should never be any risk of a quick powerwash
Or, Disconnect from the VPN before you shut down. You can connect again after startup.
I’m hoping this is the reason why, thanks