This guide can help you troubleshoot issues you encounter while you use Sign in with Google to sign in to third-party apps and services or when you allow third-party apps and services to have access to some of your data. A third party is a company or developer that isn’t Google.
Learn more about Sign in with Google and how to share some access to your Google Account with third-party apps.
Troubleshoot account login issues
Important:
- To use Sign in with Google or to share access to some of your data, you need to sign in to your Google Account.
- When you sign in with Google or share access to some of your data, your Google Account and third-party account remain separate.
If you have an issue with your third-party connections, find out whether the problem comes from your Google Account or the third-party account.
Your Google Account or third-party account is suspended or disabledWhen you try to use Sign in with Google or share access to some of your data, you could get a message that your account is disabled or suspended. You should first check if your Google Account is disabled. If it’s not, the third party may have disabled your account on their site.
- To find out whether your Google Account is disabled:
- Try to sign in to your Google Account. If your Google Account is disabled, when you try to sign in, you’ll get a message that says "Account disabled."
- Check your logins to Google services. For example, if you can log in to the Gmail address of your Google Account, then your Google Account isn’t disabled.
- If you saved another email address in your Google Account, check there for an email that says your Google Account has been disabled.
- If your Google Account is disabled:
- Try to sign in to the app or service in another way.
- Ask the third party if you can use an email and password or another sign-in method.
- Learn how to restore your account.
- Try to sign in to the app or service in another way.
- If the third party suspends your account: To get help, contact the developer directly.
- Your Sign in with Google data is also deleted, which includes your sign-in credentials for the third-party site. That means you can no longer use the Sign in with Google button to sign in with the deleted account.
- Even if your Google Account is deleted, you may still be able to access your separate third-party account in another way. Try to sign in to the app or service with a username and password, or contact the developer directly. You can also try to create new sign-in credentials on the third-party site.
- If you delete your Google Account, you also delete all associated third-party connections. The third-party app or service may keep information you previously shared with them. You may need to ask the third-party app to delete any data they already have.
- If you delete your third-party account, your Google Account is unaffected, because third-party accounts and Google Accounts are independent of each other.
- The third party doesn’t notify Google even if you used Sign in with Google to create that account. Your Google Account might still show the app or service is linked to your account.
- To understand how the third party handles your data, review their Terms of Service. Some third parties simply disable your account. Others delete your data from their service.
- If your data is deleted, you need to create a new account on the app or service. You can still use Sign in with Google to do this, but you may need to use a different Google Account.
- To stop sharing your data with a third-party app or service, remove them from your connections management page. This revokes any access that you have previously granted them.
If you already have an account on an app or service and try to use Sign in with Google, you might get an error message.
Third-party services use Sign in with Google in different ways. Some services don’t support different sign-in methods for the same account. If you run into this issue, contact the developer directly.
Understand & fix error codes
If you’re signed in to your Google Account but still can’t use Sign in with Google or grant third-party access to your 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 or service 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, so you can resolve the problem or contact the developer directly for a solution.
400 access_ not _configuredIf you get an error that says “400 access_not_configured,” 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 an error that says “400 admin_policy_enforced” it means the administrator of your account doesn’t allow you to use Sign in with Google or 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 an error that says “400 invalid_request” or “Access blocked, 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 third-party apps and services. 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 third-party developer can fix this issue. To report the error, contact the developer directly.
If you get an error that says “400 invalid_scope,” 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 third-party developer can fix this issue on the app. To report the error, contact the developer directly.
The user account being used is inactive.
What can you do about this error?
Use another valid, active Google Account.
If you get an error that says “400 origin_mismatch” or “400 redirect_uri_mismatch,” it may mean either:
- The app or service’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 help protect your account, before third parties 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 third-party developer can fix this issue. To report the error, contact the developer directly.
If you get an error that says “400 policy_enforced,” your Google Account may be part of the Advanced Protection Program. To help protect your account, this security feature doesn’t let most third-party apps or services 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 help protect your account, before a third-party 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 or service isn’t registered with Google anymore.
- 401 disabled_client: The app is blocked.
What can you do about this error?
Only the third-party developer can fix this issue. To report the error, contact the developer directly.
If you get an error that says “403 access_denied,” it means you are 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 an error that says “403 disallowed_useragent,” the app uses embedded WebViews. Some developers use WebViews to help display web content in an app. Embedded WebViews puts your security at risk because they could let third parties 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 third-party 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 an error that says “403 invalid_account,” 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 an error that says “403 org_internal,” 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 or service.
What can you do about this error?
If you’re a member of the organization, switch to your member account.
If you get an error that says “403 rate_limit_exceeded,” this 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 an error that says “403 restricted_client,” it means the third-party app isn’t set up correctly. To help protect your account, Google asks third-party developers to follow certain security requirements.
What can you do about this error?
Only the third-party 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 third-party app or service
Sometimes you can sign in to a third-party site with Google but you still can’t use the app or service. Google doesn’t fulfill the services offered by the third party, so most of the reasons this happens are outside Google’s control. We only help the app or site identify who you are.
Some examples of problems with an app or service might include:
- You bought a movie on a third-party service but can’t watch it.
- You can’t buy something on a third-party site.
- 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 a third-party app developer
To find contact info for a third-party developer:
- Go to the app or service.
- To share some of your Google data, click Sign in with Google or the call to action button.
- To get the Sign in with Google screen, you might need to sign out of the app or service.
To get the developer’s email, at the top of the next screen, select the app or website name. In some cases, the developer's email may not be available.
Secure a hacked or compromised account
- If you think someone has hacked into your Google Account: Follow the steps to secure a compromised Google Account.
- If your Google Account is hacked, someone else might be able to use your account to sign in to a third-party app or service. To strengthen your account security, turn on 2-Step Verification.
- Google helps keep your linked accounts safe with Cross-Account Protection. This program detects suspicious events and shares security notifications with compatible third-party apps and services connected to your Google Account.
- If you think someone hacked into your third-party account, contact the developer directly.
Related resources
- Manage connections between your Google Account and third-parties
- Learn more about Sign in with Google
- How Sign in with Google helps you share data safely
- Share some access to your Google Account with third-party apps
- Google Account Linking with third-party apps and services
- How Google helps you share data safely using Google Account linking