Seeing “Something went wrong” when you try to sign in to Google can be frustrating because the message does not identify a single cause. It may relate to your browser, connection, account verification, device settings, or the app you are using. Work through the checks below in order, starting with the quick ones. You will need access to your Google account’s recovery options if Google asks you to verify your identity. Never share a password or verification code with someone who contacts you unexpectedly.
What You’ll Need
- A phone, computer, or tablet with an internet connection and a browser or Google app.
- Your Google account email address and password, if you know them.
- Access to a recovery phone, recovery email, or a device where you are already signed in, in case Google requests verification.
- If this is a work or school account, the option to contact your organization’s Google Workspace administrator.
Step-by-Step
- Check the connection and try again once. Open a familiar, secure website to confirm that your internet connection works. If it does not, reconnect to Wi-Fi or mobile data, or restart your router if you control it. If the connection is working, reload the Google sign-in page and make one careful attempt. Repeated rapid attempts can trigger additional security checks, so avoid submitting the form over and over.
- Confirm that you are on a genuine Google sign-in page. Check that the address bar shows a Google-owned domain, such as accounts.google.com, before entering your password. If you reached sign-in through an app or a link, close the page and open the service directly from its official app or website. Do not enter your credentials into a page reached through an unexpected email, text, or pop-up.
- Check the account details. Make sure you selected the right Google account and entered its full email address correctly. If you use several accounts, try the one that owns the service or files you are trying to reach. If you are unsure of the address, use Google’s account-recovery flow to find or recover your account rather than guessing repeatedly. If you recently changed your password, use the new one and update it in any password manager that fills the old one automatically.
- Try a private or incognito browser window. Open a private window and visit the Google sign-in page directly. This provides a useful test because it usually starts without your existing cookies and may not load your usual extensions. If sign-in works there, the problem is likely connected to stored site data, a browser setting, or an extension in your regular window. Private browsing is a diagnostic step, not a way to bypass account verification.
- Temporarily check browser extensions and privacy settings. In your regular browser, turn off extensions that block scripts, ads, tracking, or pop-ups one at a time, then retry sign-in. You can also try another up-to-date browser. Google sign-in may need cookies and scripts to work; if your browser blocks them, allow the necessary content for Google’s sign-in page. Avoid broadly weakening privacy or security settings. If a change does not help, restore the setting.
- Clear Google site data if the private-window test worked. Before deleting anything, note that removing cookies can sign you out of websites. In your browser’s privacy or site-settings controls, remove cookies and cached data for Google sign-in or the affected Google site, then close and reopen the browser. The wording varies by browser. You do not usually need to erase all browsing history or saved passwords. Return to the official sign-in page and try again.
- Update the app, browser, and device. If the error appears inside an app, update that app through its official app store and try signing in again. On a computer, install available updates for your browser. On Android, update Google Play services and the Google app through Google Play if updates are available; on iPhone or iPad, update the app and iOS or iPadOS when practical. Restarting the device after updates can clear a temporary software problem.
- Check device time and network restrictions. Set the device’s date, time, and time zone to update automatically where that option is available, then restart it. An inaccurate clock can interfere with secure connections. If you are on a workplace, school, hotel, or public network, its sign-in page, firewall, or filtering rules may interfere. Try a trusted different network, such as your own mobile connection, if available and safe. Do not use an unfamiliar public computer to save your password.
- Complete Google’s verification prompts carefully. If Google asks you to confirm it is you, use the on-screen options and a device or recovery method that belongs to you. Approve a prompt only when you initiated the sign-in. Enter a code only on Google’s sign-in page; never send it to another person. If you no longer have a recovery phone or email, follow the account-recovery questions and provide the most accurate information you can.
- Retry the original service after Google sign-in works. If you were signing in to another app or website with the “Sign in with Google” button, first confirm that you can sign in to your Google Account directly. Then return to the service and start its Google sign-in flow again. If Google sign-in succeeds but the other service still fails, the issue may be with that service’s account connection rather than your Google password.
Common Mistakes
Changing the password before checking the cause: A password reset may help if the password is wrong or the account is compromised, but it will not fix a blocked cookie, an outdated app, or a network problem. Resetting it unnecessarily can also mean updating the password on other devices and apps. First identify whether you can sign in through a browser and whether Google is asking for a specific verification step.
Repeatedly submitting the same attempt: Fast, repeated retries do not make a vague error clearer and may lead to more security prompts. Pause, check the connection and account details, then retry after making one change at a time.
Clearing everything or disabling security tools: Erasing all browser data can remove useful sessions and preferences without addressing the cause. Turning off antivirus protection, a firewall, or all browser privacy protections is also risky. Prefer a private-window test, a different browser, or a temporary, targeted extension check; restore settings that do not solve the problem.
Approving a sign-in you did not start: Never approve a Google prompt or share a verification code just because someone says they are helping. If a prompt appears unexpectedly, deny it and review your account security using Google’s official account settings.
Tips
- Make one change at a time and note whether the error changes. This helps distinguish a browser issue from an account or app issue.
- If you are already signed in on another trusted device, use it to check your Google Account security settings and confirm that your recovery information is current. Do not sign out of that device until you know you can get back in.
- When you use a password manager, check that it is filling the correct account and current password. A saved password can be out of date even when the account address is right.
- For a managed work or school account, avoid removing administrator-installed profiles or changing organization security settings yourself. Ask the administrator whether access policies or a required verification method are affecting sign-in.
- Use only Google’s official recovery pages and help resources. Search results, support advertisements, and unsolicited messages can lead to third-party services that cannot recover a Google Account for you.
Troubleshooting
The error appears in every browser and on more than one device: This makes a problem limited to one browser less likely. Check whether you can access your account from a device where you are already signed in, and follow any account alert or recovery prompt shown there. If you cannot sign in anywhere, use Google Account recovery and answer as accurately as possible. Avoid repeated guesses or unofficial recovery services.
It works in a private window but not your usual browser: Recheck cookie restrictions and extensions in the normal browser. Remove Google site data, restart the browser, and test again before enabling extensions one by one. If you use a browser profile with strict privacy settings, test a clean profile without changing the security settings on your main profile.
It works on mobile data but not Wi-Fi: The Wi-Fi network may have a sign-in portal, filtering rule, or other restriction. Complete the network’s legitimate connection steps, or ask its administrator for help. If it is your home network, restart the router and check its filtering settings. Do not change settings you do not control.
The problem is limited to one app or website: Update the app, close and reopen it, and try its Google sign-in button again. If you can access Google directly but the app still fails, contact that app’s official support. For a work or school service, contact your organization’s administrator. Explain what device and browser you used and whether direct Google sign-in succeeds; never include your password or verification code.
You cannot complete identity verification: Use Google’s account-recovery process from a device and location you commonly use, if possible, and provide information that matches the account. If a recovery option is unavailable, follow the alternatives shown by Google rather than repeatedly requesting codes. A work or school account may require help from its administrator. No one outside the account’s recovery process should ask you to disclose your password or codes.
You suspect someone else accessed the account: If you can sign in on a trusted device, review recent security activity, change the password to a unique one, and check recovery details and signed-in devices. Follow Google’s account-security guidance. If you cannot sign in, use account recovery promptly. Do not approve prompts you did not initiate.
Frequently Asked Questions
Does “Something went wrong” mean my Google Account is disabled?
No. The message alone does not establish that an account is disabled. Try the browser and device checks above. If Google says the account is disabled or asks for recovery, follow the specific instructions on the official sign-in page.
Will clearing cookies delete my Google Account?
No. Clearing browser cookies removes local website data and may sign you out, but it does not delete the account itself. You will need to sign in again, so make sure you know the account address and can complete verification first.
Why does Google sign-in work in a browser but not an app?
The app may be outdated, may have a temporary sign-in issue, or may have a problem linking to Google. Update and restart it, then try its official sign-in flow again. If only that app fails, contact its support rather than repeatedly resetting your Google password.
Should I use a VPN to fix this error?
A VPN is not a general fix. A network location change can sometimes lead to additional verification, and a work or school network may have its own rules. Try a trusted network you control, and follow Google’s verification prompts instead of using a VPN to bypass them.
How long should I wait before trying again?
There is no single wait time that applies to every sign-in error. If you have made many attempts, stop retrying briefly, check for a specific message or verification request, and use account recovery if needed. Follow any wait instructions Google displays on screen.