Google says “Couldn’t sign you in” and “This browser or app may not be secure”? Your password is usually fine. Google is refusing the sign-in because it does not trust the browser or app you are using. The fix depends on which of a few causes applies, and most take a minute to check.
Quick answer: Open a current version of Chrome, Safari, Firefox, Edge or Opera in a normal window, turn on JavaScript, disable extensions, and try again. If the message appears inside an app (not a browser), the app is probably using an embedded browser that Google blocks, so sign in through the app’s website or contact its developer.
Documentation reviewed November 1, 2026. The steps below come from Google’s own help pages, listed at the end. Google does not publish every cause of this message, so anything beyond those pages is labelled as a user report. Menu names can change.
What this error means
Google’s help page on supported browsers says it may stop sign-ins from browsers that:
- do not support JavaScript, or have it turned off
- have unsecure or unsupported extensions installed
- are controlled by automation software instead of a person
- are embedded inside another application
Google lists Chrome, Safari, Firefox, Opera and Edge as supported browsers. The fixes below go through each cause in order.
First, match what you see to the fix
| What you see | Likely cause | Go to |
|---|---|---|
| Error in a normal browser window | Unsupported browser, old version or JavaScript off | Fixes 1–3 |
| Error only with certain add-ons installed | An extension Google does not trust | Fix 4 |
| Error after a privacy or security setting change | Strict privacy mode, firewall, proxy or antivirus | Fixes 5–6 |
| Error inside an app or a “Sign in with Google” button | Embedded browser or app problem | Fix 7 |
| Old email app or device that asks for a password | App needs an app password | Fix 8 |
Fix 1: Use a supported browser in a normal window
Try signing in with Chrome, Safari, Firefox, Edge or Opera. Avoid browsers that are not on that list, and avoid signing in from inside another app’s built-in browser, such as the browser that opens when you tap a link in some apps. Open a fresh normal window and go to accounts.google.com directly.
Fix 2: Update your browser
Google says old browser versions may not be supported. Update the browser, restart it and try again. Users have also reported this message appearing on one specific browser version and disappearing after an update. For example, a September 2022 thread on the Brave community forum described a user whose Chrome showed the error until it updated to a newer release. That was one report, not a general rule, but updating is a cheap first step.
Fix 3: Turn on JavaScript
Google’s steps for Chrome on Android: open Chrome, tap More, then Settings. Under Advanced, tap Site settings, then JavaScript, and turn it on. You can turn it off again after you have signed in. On other browsers, check that browser’s support page for how to enable JavaScript.
Fix 4: Turn off extensions
Google says to disable unsecure or unsupported extensions and re-enable them after signing in. The quickest test is a private or incognito window with extensions off, or a browser profile with no extensions. If the error disappears, turn extensions back on one at a time to find the one causing it.
Fix 5: Check privacy settings
Google says that if a browser other than Chrome has its privacy level set to High or Strict, you should add google.com to its allowed sites. Browsers that block cookies or scripts aggressively can break the sign-in page.
Fix 6: Check your firewall, proxy, VPN and antivirus
Google suggests temporarily turning off a firewall, proxy or antivirus program. If that fixes the sign-in, contact that program’s support to ask how to allow Google access, then turn it back on. Do not leave security software off. If you are on a work computer, ask your administrator about company security settings.
Fix 7: The error appears inside an app
If you see the message from a desktop or mobile app, the app may be using an embedded browser. Google’s page on sign-in error codes lists “403 disallowed_useragent” for this case: the app uses embedded web views, which Google stopped allowing on September 30, 2021. Google’s advice is to contact the developer, and, if the app has a website, sign in through your regular browser instead.
Other errors from the same Google page that you might see with “Sign in with Google”:
- “400 admin_policy_enforced”: your organization’s administrator does not allow the sign-in. Contact your Google Workspace administrator.
- “400 policy_enforced”: your account is in the Advanced Protection Program, which blocks most third-party app access.
- “403 access_denied”: you are not authorized, for example because the app is in test mode or the account type is restricted.
- “403 invalid_account”: your Google Account may be disabled. Check whether it is, and follow Google’s steps to restore it.
- “400 invalid_request” or “Access blocked”: the app uses an authorization method Google does not allow. Only the developer can fix this.
If you hit a blocked-authorization error while connecting ChatGPT to Google, see our guide to the Google Drive connector not working.
Fix 8: Old email apps and devices that ask for a password
Some older apps and devices cannot use Google’s normal sign-in. Google’s guidance is to use “Sign in with Google” if the app offers it. If it does not, you can create an app password, a 16-character code, from your Google Account. Google calls app passwords not recommended and usually unnecessary. They require 2-Step Verification to be turned on, each one can only be entered once, and changing your Google Account password revokes all of them. If a non-Google app still cannot sign in, Google says its sign-in process may not be secure, so update the app or switch to a more secure one. Remove any app password you no longer use.
When it might not be a browser problem
If you also get a “Verify it’s you” prompt, an unexpected sign-in alert or a password that suddenly stops working, treat it as a possible account problem rather than a browser one. Google’s help pages direct people to secure a compromised account and to turn on 2-Step Verification. Do not enter your password or verification codes on any page you reached from a link in an email or text message, and note that Google says it never asks for your password or verification codes by email, phone or message. Start from accounts.google.com yourself.
Still not working? Collect these details
- The exact error text and the screen it appears on
- Your browser and its version, or the app name
- Whether it happens on another device or network
- Whether it happens in a private window with extensions off
- Whether the account is personal or a work or school account
FAQ
Does “this browser or app may not be secure” mean my account was hacked?
Not by itself. Google lists unsupported browsers, missing JavaScript, unsupported extensions, automation and embedded browsers as reasons it may block a sign-in. If you see other warning signs, check your account security separately.
Why does Google block embedded browsers?
Google’s error-code page says it stopped allowing embedded web views for sign-in on September 30, 2021. Apps that still use one show “403 disallowed_useragent”, and the developer has to change how the app signs in.
Which browsers does Google support for sign-in?
Google’s help page lists Chrome, Safari, Firefox, Opera and Edge.
Should I use an app password to get around the error?
Only for an old app or device that cannot use Google’s normal sign-in, and only if “Sign in with Google” is not available. Google says app passwords are not recommended and need 2-Step Verification.
Sources: Google Account Help: Sign in with a supported browser, Understand and fix error codes, Sign in with app passwords, and the Can’t sign in to your Google Account troubleshooter; a Brave community thread for the browser-version report. This is a documentation-based guide, not a claim of hands-on testing on every browser.
Part of our AI security and privacy guides.
