Chromebook Error 400

[WannabrewUK]

The last few days we've noticed a lot of our Chromebooks coming up with Error 400 when trying to login.

 

Whatever the cause it's very intermittent. one second it doesn't work, try again and it does, try again a few minutes later and it doesn't again.

 

Anybody else experiencing anything similar?

[6Foot2]

I have an ASUS C523N (not enrolled on a domain) Not seeing any similar issues.

[techedu07]

Any errors that I see on a Chromebook, I usually Powerwash them to remove data/cache etc.

[paulkerton]

The last few days we've noticed a lot of our Chromebooks coming up with Error 400 when trying to login.

 

Whatever the cause it's very intermittent. one second it doesn't work, try again and it does, try again a few minutes later and it doesn't again.

 

Anybody else experiencing anything similar?

 

Just curious... Who is your ISP?

[WannabrewUK]

Schools Broadband, I've opened a support ticket with them.

[WannabrewUK]

Just an update..

 

It appears to be a problem with some settings on the ISP managed firewall. I opened a support ticket with them, and they made some changes yesterday hoping to fix things, but it's even worse now.

 

Before it was intermittent, so if you couldn't login you could try a few more times and chances are it would work. Now nobody can login to a Chromebook in the whole of school. That's 200+ devices not working this morning.

[EssentialRug]

Seeing this issue too but our ISP is RM...

[WannabrewUK]

We've tried a powerwash on a couple of devices for testing purposes. We can't re-enroll them because they're not able to talk to google.

[6Foot2]

We've tried a powerwash on a couple of devices for testing purposes. We can't re-enroll them because they're not able to talk to google.

 

Get them re-enrolled by (temporarily) using a mobile hotspot?

[Affray]

We seem to be getting random ones getting 400 error, ChromeOS flex and Chromebook proper, some work when restart, but otherwise, I've had to deprovision them factory reset and same model replacement. Then (after adding it the openest wifi) I do not enrol it and sign in with a work account and it updates, then I enrol it (it powerwashes) go through the normal enterprise enrolment and it seems fine.

I think its an Update with the Enterprise Admin Google side, but am not sure. Hmm we just had to sign in on the unfiltered wifi to get it to work the first time, seems alright after a reboot.

[dslater]

We are also having the issue, here's a fix (Does not work all the time) : On the login screen turn off the wifi, wait 10 seconds and turn it back on. You'll know its worked because the "Next" button will reappear on the login (if its not there you will always get the error). Sometimes it wont reappear after the first wifi on/off so id try this a couple times to see if it works. If this fails, try power washing the machine then doing the same thing.

[pacapps]

Hi, We are having this issue as well.

 

I thought we (SBB and I) had broken it as we were looking at filtering issues on chromebooks at the time.

 

Sometimes the button is greyed out, other times not there at all.

I did powerwash but then had to connect via a hotspot to re enroll (in a very dodgy signal area).

 

Switching between hotspot and our wifi either breaks it or fixes it.

 

Wish I had found this thread yesterday!! I have spent 2 (stressful) days chasing my tail trying to get this resolved to only now find out its not just us :-)

 

Of course SBB didnt let on that fact.

[msi_school]

I have just been sent this form our central team

 

Official update from Google:

 

 

Your Case # for Chrome has been updated.

Case Subject: Getting error 400 when logging on to a ChromeOS device

Case Comment :

After reviewing the information you provided, we believe that you may be affected by an issue we've become aware of: Error 400 when signing in to Chromebooks. This is a high priority issue that we're working to resolve as soon as possible. Here are some details about the issue:

 

Status:

Investigating

 

Description:

Multiple customers are reporting that they are unable to sign in to Chromebooks and get the error ""400. That's an error. The server cannot process the request because it is malformed. It should not be retried. That's all we know."

 

How to diagnose:

1.User tries to login using their username and password

2. Gets the error "400. That's an error. The server cannot process the request because it is malformed. It should not be retried. That's all we know."

 

Workaround:

There's no workaround available at this time, but we'll let you know if we learn of one.

 

Current update:

At 2023-12-14 13:04 UTC (just now):

We are investigating the issue.

Meanwhile could you allow list http://www.gstatic.com as mentioned here https://support.google.com/chrome/a/answer/6334001?hl=en and let us know if it helps to resolve the issue.

Please review your case and take any actions as requested. If you have any questions or require immediate assistance, please reply to this email to contact Google Workspace Support.

You can also view and comment on your case by logging into our support portal

 

Thanks for choosing Google Workspace.

—The Google Team

[Affray]

Got to say we've had some we though were fixed come back thanks for the update, I was stuck on number 2 on Google support for 30 minutes so gave up.

gone back to have another go at google, number 2 again.

If it was the TV show "The Prisoner" I'd be happy....

Edited December 14, 2023 by Affray

[WannabrewUK]

I know it's early doors, but I've not had it happen once so far today. I've probably just Jinxed myself by saying the issue appears to have been resolved for us.

 

Anybody else seeing the same?

[Affray]

Same here, seems to be *fixed*, 4 with 400 I had in the office seem to work fine now.

 

14 Dec 2023 23:44 UTC

Our Engineers have taken measures that would mitigate the issue. Please confirm if this issue is still present within your environment after trying again. If the issue persists please submit a feedback report [https://support.google.com/chromebook/answer/2982029?hl=en] (please use the internal bug number: 316308801 and a message that it was recorded "after a login failure" )

14 Dec 2023 19:11 UTC

This issue is still under investigation. In the meantime can you confirm if this issue is still currently present? If this issue is still present for new reports please submit a feedback report [https://support.google.com/chromebook/answer/2982029?hl=en] (please use the internal bug number: 316308801 and a message that it was recorded "after a login failure" )

Edited December 15, 2023 by Affray

[mismafia]

Is anyone else still having this issue? We had the issue start Nov. 13, 2023. It was really bad the first few weeks but did get better..... but we are still seeing it enough to be annoying. They either get "you are not authorized to log into this device" or "error 400 the server cannot process the request bc it is malformed." If the student powers down (sometimes take multiple tries), they typically can get in.

[Accura2k7]

We had this, its a firewall/filtering issue. I wasnt involved in the fix though, just figuring out exactly what was going on.

[mismafia]

what steps did you take to determine it was fw/filtering issue?

[mismafia]

Is it possible to find out what changes were made to fix it?

[Accura2k7]

Bounce one through a hotspot, issue goes away, filtering/firewall, stays its device.

 

We worked closely with Google on this, i wasnt involved in the end result though.

[mismafia]

It happens to students even at home and hotspot at school.

I ran across something interesting yesterday - My original setting for "DeviceShowUserNameOnSigin" was set to "never show user names & photos." If I change that to "always show user names and photos," I cannot replicate the errors after trying 10 plus times to log on. Once I change it back to "never show user names & photos" and tried to log in, I immediately got the "you are not authorized to use this device:" error. Reported to Google...their response: t has to do something with the User data that gives you guys the Error & they will research.

[philellis]

did anyone ever get to the bottom of a fix for this issue?

 

Thanks

Edited March 15, 2024 by philellis

[mismafia]

We did not. I'm still using the work around - applied setting "always show usernames & photos" on log on screen. For some reason when the user logs on this way, they never get error. Google still claims they fixed the bug but obviously they did not! It was strange because my school was the only one in my district that was seeing the issue... but yesterday our middle school starting getting it intermittently.

[WannabrewUK]

We've not seen the issue in months, just started to see it again today.