Why Does Gemini Keep Saying Something Went Wrong? | Fix Now

You’re typing a prompt, you hit send, and Gemini answers with the same dull line: “Something went wrong.” It’s annoying because it doesn’t tell you what failed. It also wastes time when you’re mid-task and the chat won’t move.

The good news: this error is rarely “mystery.” Most cases come down to a small set of repeat offenders: stale login sessions, browser storage issues, extensions that block scripts, VPN or DNS quirks, or a short outage. This article walks you through a clean, step-by-step way to pin down the cause and fix it without guesswork.

What “Something Went Wrong” Usually Means

That message is a catch-all. It can show up when the page can’t finish a request, when your account session can’t refresh, or when the service refuses the request for a policy or rate reason.

Think of it as “the app didn’t get a usable response.” The trick is to figure out which layer broke: your device, your browser/app, your Google account session, your network, or the service side.

Fast Triage In 2 Minutes

Start with the tests that change one thing at a time. You’re not trying random fixes. You’re narrowing the cause.

Step 1: Refresh And Retry In A New Chat

Reload the page or fully close and reopen the app. Then start a new chat and send a short prompt like “Say hi.” A single chat thread can glitch after long sessions, heavy attachments, or rapid-fire prompts.

Step 2: Try Another Network

Switch from Wi-Fi to mobile data, or use a different Wi-Fi. If it works on the other network, you’ve learned the problem sits in your original connection, DNS, firewall rules, or VPN stack.

Step 3: Try Incognito Or A Fresh Profile

Incognito disables many extensions and starts with cleaner storage. If the error vanishes there, you’re dealing with cookies, cached files, or an extension that interferes with login or requests.

Step 4: Sign Out, Then Sign In Again

If your account token is stale, you can be “logged in” yet not truly authorized for the next call. Signing out and back in forces a clean session renewal.

Common Causes And How To Spot Them

Now that you’ve done the quick tests, use the patterns below to match what you’re seeing to the most likely cause. Then you’ll apply the fix that fits.

Fix The Browser Version First

If you use Gemini in a browser, your top suspects are cookies, cached files, and extensions. Most “Something went wrong” loops end when you clean up those three.

Clear Site Data For Gemini Without Nuking Everything

Clearing all browser data can be overkill. Start by clearing data just for Gemini. In Chrome, you can remove cookies and site data for a single site from your privacy settings, then reload and sign back in.

If you’d rather follow Google’s own steps for clearing cache and cookies, use this official walkthrough: Clear cache & cookies. After you clear them, expect to sign in again.

Check Cookie Blocking And Privacy Shields

Gemini depends on Google account sessions and web storage. If you block cookies too aggressively, the session can’t refresh and the page can fail mid-request.

On Chrome, review your cookie settings and site exceptions. Google’s guide on cookie controls is here: Delete, allow, and manage cookies in Chrome. Focus on allowing cookies for Google sign-in flows and the Gemini site.

Disable Extensions That Intercept Web Requests

Ad blockers, script blockers, privacy extensions, antivirus web shields, and “coupon” extensions can all break modern web apps. Don’t guess. Turn them off one at a time, reload, then retry the same short prompt.

If it starts working after you disable one extension, you’ve found your culprit. Keep it off for the Gemini site, or add a site exception inside that extension’s settings.

Update Your Browser And Restart It Fully

Outdated builds can mis-handle newer web features. Update Chrome, Edge, Firefox, or Safari. Then fully quit the browser and reopen it, not just close the window.

Try A Clean Browser Profile

If the error persists in normal mode even after clearing site data, create a fresh profile and test there. A clean profile rules out hidden settings, damaged local storage, and legacy permissions.

Fix The Mobile App Version

On mobile, the same themes apply: stale app cache, network switching, and account session hiccups. The difference is where you clear data and how you reset the session.

Clear App Cache And Restart Your Phone

On Android, clearing the app cache is a strong first move. Then reboot your phone. A reboot resets network stacks and background services that can get stuck.

Update The App And Your System Web Components

Update the Gemini app and your browser (Chrome on Android, Safari on iOS). Many apps lean on system web components for sign-in and embedded pages, so stale system parts can trigger odd sign-in failures.

Check VPN, Private DNS, And “Secure Wi-Fi” Features

VPNs and private DNS can break token refresh calls or route you through a blocked region. Turn off the VPN, try again, and only turn it back on after you confirm Gemini is stable.

Some mobile security apps run “secure browsing” filtering. If disabling the VPN fixes the error, test with private DNS off too, then re-enable features one at a time.

Why The Error Can Be Account-Specific

Sometimes the device and browser are fine, yet one account fails while another works. That points to an account state issue, not a local glitch.

Test With A Second Google Account

If you have another account, sign in with it in the same browser profile. If the second account works right away, your first account has a setting or state that’s blocking the request flow.

Check Activity And Access States

Gemini ties into Google account services and activity controls. A stuck activity toggle or a delayed sync can trigger repeated request failures that show as “Something went wrong.”

Report The Problem From Inside The App

If you’ve ruled out browser/app cache and network issues, report it. Google’s Gemini support forum threads also list basic steps like refresh, restart, and device reboot, which match the first-line fixes many users need. One example thread is here: Keeps saying “something went wrong” (9).

Taking A Closer Look At Network Problems

If Gemini works on one network and fails on another, don’t keep clearing cookies. Focus on the network path. This is where hidden blockers live.

Captive Portals And Filtered Wi-Fi

Hotels, airports, schools, and workplaces often use captive portals. Your browser might be “connected” yet blocked from full access until you accept terms. Open a plain HTTP site in a browser to trigger the login page, then try Gemini again.

Router Reboot And DNS Switch

Reboot your router and modem. Then test again. If the issue persists, try switching DNS to a well-known public DNS provider inside your router or device settings, then retest.

Firewall And Security Software Inspection

Some security tools intercept HTTPS traffic or block “unknown” endpoints. Temporarily pause web filtering and test. If that fixes it, add an allow rule for Gemini and Google sign-in domains inside the tool.

When The Service Side Is The Real Cause

Sometimes you’re doing everything right and the service is having a rough patch. You’ll see the error across devices, browsers, and networks, often for a short window.

Rate Limits And Rapid Requests

If you fire off many prompts back-to-back, you can hit throttles. Slow down, wait a bit, then retry with a short prompt. If it works, your account was likely being throttled for a short stretch.

Temporary Outages And Partial Failures

Outages aren’t always “all down.” You can load the page and still fail on requests. If your troubleshooting points to a service-side issue, the best move is to pause, then retry later with a clean session.

Why Does Gemini Keep Saying Something Went Wrong? Common Patterns And A Clean Fix Order

If you want one reliable sequence that fits most cases, use this order. It keeps the fixes low-risk and narrows the cause as you go.

Clean Fix Order

• Reload the page or restart the app, then test a short prompt in a new chat.
• Try Incognito (or a fresh browser profile). If it works there, focus on cookies, cache, and extensions.
• Clear site data for the Gemini site, then sign back in and retry.
• Disable blockers and privacy extensions, one at a time, then retry after each change.
• Switch networks or disable VPN and private DNS, then retry.
• Test with a second Google account to confirm whether it’s account-specific.
• Update your browser/app, reboot the device, and retry with a clean session.

Platform Checklist You Can Run Anytime

Small Habits That Prevent Repeat Errors

If you hit this error often, it’s usually because the same underlying trigger keeps returning. A few habits can cut it down a lot.

Keep One Browser Profile Clean

Use one profile for tools like Gemini. Keep extensions minimal. If you love heavy privacy add-ons, run them in a second profile and keep the “work” profile calmer.

Avoid Piling Everything Into One Chat Thread

Long chats can collect state that sometimes glitches. When a thread feels sluggish, start a new one and paste only the pieces you still need.

Keep VPN Rules Simple

If your VPN has split-tunneling, set the Gemini site to bypass it. If you can’t, toggle the VPN off while you run Gemini tasks that keep failing, then turn it back on after.

When You Should Stop Troubleshooting And Escalate

If you’ve tested another browser profile, another network, and another account, and the error still loops, you’ve already done the highest-value local checks. At that point, your best move is to report the problem through Gemini’s help flow and include the rough time, device, browser/app, and what you tried.

That report gives Google what it needs to spot account-side failures or service-side faults tied to specific regions, networks, or account states.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback