If you’re signed in to your Google Account but still can’t use Sign in with Google or grant an app from a developer other than Google some access to your Google Account data, you might get an error code and message.
Some issues that cause an error message may be outside of Google’s control. For example, the app you want to use could be set up in an unsafe way that Google doesn’t allow.
Error codes help you understand why you can’t sign in or grant access to your data. You can resolve the problem or contact the developer directly for a solution .
Learn how to fix account-related issues with linked apps .
400 access_ not _configuredIf you get a “400 access_not_configured” error, it means the app has not been properly configured by a Workspace for Education Administrator.
What can you do about this error?
If this is an app you expect to be able to use, contact the Workspace administrator to configure access for the app.
If you get a “400 admin_policy_enforced” error, it means the administrator of your account doesn’t allow you to use Sign in with Google. Also, you can’t share some of your organization-specific data with the app.
This can happen when you use an account from work or another organization. Sometimes only specific apps are blocked.
What can you do about this error?
If you believe you should have access to the app, reach out to your organization’s Google Workspace administrator.
If you get a “400 invalid_request” or “Access blocked” error, it means the app sent an invalid request. The app uses an authorization method that Google doesn’t allow.
Google has safe ways for you to sign in and share your Google Account data with apps from developers other than Google. To help protect your account, Google blocks apps that could put your account at risk.
Tip: Learn how Sign in with Google shares your data safely .
What can you do about this error?
Only the app developer can fix this issue. To report the error, contact the developer directly .
If you get a “400 invalid_scope” error, it means the app asks for a permission that we don’t recognize or they aren’t allowed to ask for.
What can you do about this error?
Only the app developer can fix this issue on the app. To report the error, contact the developer directly .
If you get a “400 invalid_user” error, it means your account is inactive.
What can you do about this error?
Use another valid and active Google Account.
If you get a “400 origin_mismatch” or “400 redirect_uri_mismatch” error, it may mean either:
- The app’s developer hasn’t set up their app correctly.
- The app has tried to access your data in a way that doesn’t follow our policies.
To protect your account, before these apps can use Sign in with Google, we require them to register their app with us. They must also follow our security standards and policies. If an app doesn’t follow these policies, we won’t let it use Sign in with Google until the app developer fixes the problem.
What can you do about this error?
Only the app developer can fix this issue. To report the error, contact the developer directly .
If you get a “400 policy_enforced” error, your Google Account may be part of the Advanced Protection Program . To help protect your account, this security feature doesn’t let most apps from developers other than Google access your Google Account data.
What can you do about this error?
To fix this error, you must opt out of the Advanced Protection Program . This means you’ll lose the program’s security benefits.
If you get an error that starts with “401,” that usually means the developer didn’t properly register their app with Google.
To protect your account, before an app developer can use Sign in with Google or request access to some of your data, Google asks them to register their apps. We don’t share your info with the developer until they register with us.
Some of the error messages you might get include:
- 401 invalid_client:Either the app doesn't match the info on its registration or the developers haven’t given Google all the required info.
- 401 deleted_client:The app isn’t registered with Google anymore.
- 401 disabled_client:The app is blocked.
What can you do about this error?
Only the app developer can fix this issue. To report the error, contact the developer directly .
If you get a “403 access_denied” error, it means you’re not authorized to use Sign in with Google or to share some account data with the app. Some reasons for this include:
- The app is in test mode and the developer hasn’t added you as a test user.
- The type of Google Account you’re signed in to doesn’t let you use Sign in with Google or share some of your account data.
- For example, a child’s account can’t use Sign in with Google without a parent or guardian’s permission.
- Your organization administrator might also disallow you to use Sign in with Google or share some account data with certain apps.
What can you do about this error?
- Use a different type of account to sign in to the app.
- If you believe your account should have access, contact the developer directly .
If you get a “403 disallowed_useragent” error, the app uses embedded WebViews. To display web content in an app, some developers use WebViews. Embedded WebViews put your security at risk because they could let apps from developers other than Google access and change communications between you and Google.
To keep your account secure, Google no longer allows embedded WebViews as of September 30, 2021.
What can you do about this error?
- Only the app developer can fix this issue on the app. To report the error, contact the developer directly .
- If the app has a website, you can try to sign in from your browser.
If you get a “403 invalid_account” error, it may mean your Google Account is disabled.
What can you do about this error?
Check if your Google Account has been disabled .
- If you find out your account is disabled, learn how to restore your account .
If you get a “403 org_internal” error, it means that only members of a specific company or organization can use the app. For example, an organization might only allow email addresses that end in @example.com to access the app.
What can you do about this error?
If you’re a member of the organization, switch to your member account.
If you get a “403 rate_limit_exceeded” error, it means the app has reached its sign-in rate limit for now. Google limits how quickly an app can get new users.
What can you do about this error?
You can try to sign in again later, or ask the developer to increase this app's sign-in rate limit.
If you get a “403 restricted_client” error, it means the app isn’t set up correctly. To help protect your account, Google asks app developers to follow certain security requirements.
What can you do about this error?
Only the app developer can fix this issue. To report the error, contact the developer directly .
An error occurred while we were processing this request.
What can you do about this error?
Try again later.
Fix other problems on a linked app
Sometimes you can sign in to a linked app with Google but you still can’t use the app. Google doesn’t fulfill the services offered by the developer of the app, so most of the reasons this happens are outside Google’s control. We only help the app identify who you are.
Some examples of problems with an app might include:
- You bought a movie on a linked app but can’t watch it.
- You can’t buy something on a linked app.
- You shared your Google Calendar data with a calendar app but your events aren’t showing on the app.
- You shared a Google photo with a photo edit app but the photo isn’t loading.
If you have problems like these, contact the developer directly .
Contact the developer for an app not created by Google
To find contact info for an app developer:
- Go to the app.
- To share some of your Google data, click Sign in with Googleor the call to action button.
- To get the Sign in with Google screen, you might need to sign out of the app.
- To get the developer’s email, at the top of the next screen, select the app name.
- In some cases, the developer's email may not be available.
