Gemini Not Working? Fix Common Issues Fast

Overview

Gemini can stop responding, throw errors, or silently fail for reasons that range from a stale browser session to a region restriction you didn’t know existed. The fix depends on where Gemini breaks: the web app at gemini.google.com, the mobile app, the API, or an IDE integration like Gemini Code Assist.

This guide covers each failure surface separately. Work through the quick fixes first — they resolve the majority of cases in under two minutes. If those don’t help, the numbered steps below isolate the root cause by platform.

Symptoms

What “not working” looks like depends on the interface:

Web app (gemini.google.com):
– Blank page or infinite loading spinner after login.
– “Something went wrong” banner with no error code.
– Responses stop mid-generation and the input box grays out.
– “Gemini isn’t available in your country” message.

Mobile app (Android / iOS):
– App opens but the chat screen stays empty.
– Crashes on launch or immediately after sending a prompt.
– “Can’t reach Gemini right now” toast notification.

API (Gemini API / Vertex AI):
– HTTP 429 (rate limit), 403 (permission denied), or 500 (internal server error).
– Model returns empty responses or truncated output.
– “Model not found” when calling a specific model version.

IDE integrations (Gemini Code Assist, Google AI Studio):
– Autocomplete suggestions stop appearing.
– “Authentication failed” or “Session expired” in the extension output log.

Why This Happens

Most Gemini failures trace to one of five root causes:

1. Server-side outage. Google’s infrastructure is large but not immune to incidents. Gemini and Vertex AI share backend capacity, so a Vertex disruption can affect the consumer app.

2. Stale authentication. Google session tokens expire. Browser cookies get corrupted. OAuth tokens in API clients hit refresh limits. The result is identical: requests fail silently or return 401/403.

3. Region or account restrictions. Gemini features roll out unevenly across countries and Google Workspace plans. A feature that works on a personal @gmail.com account may not be enabled for an enterprise Workspace domain — and vice versa.

4. Browser or extension interference. Ad blockers, privacy extensions, and aggressive cookie policies break the WebSocket connections Gemini uses for streaming responses. Dark mode extensions that inject CSS can also cause blank-screen rendering issues.

5. API quota or configuration errors. Billing not enabled, wrong project selected, exhausted free-tier quota, or referencing a deprecated model endpoint.

Check Service Status and Account Access

Confirm the service is up:
Visit the Google Cloud Status Dashboard. Look for incidents tagged “Gemini” or “Vertex AI.” If there’s an active incident, local troubleshooting won’t help — wait for resolution and check the incident timeline for ETAs.

Verify your account:
– Go to myaccount.google.com and confirm you’re signed into the correct account. Users with multiple Google accounts (personal + work) frequently hit issues because the wrong account is active.
– For Workspace accounts: your organization’s admin controls whether Gemini is enabled. Check with your IT admin if you see “not available for this account” messages.

Test basic access:
Open gemini.google.com in a different browser entirely — not just a new tab. If it works in Firefox but not Chrome, you’ve narrowed the problem to browser-specific causes.

Clean Browser or App Session

Chrome / Edge / Brave

1. Open an incognito window (Ctrl + Shift + N on Windows/Linux, ⌘ + Shift + N on Mac).
2. Navigate to gemini.google.com and sign in.
3. If it works in incognito: one of your extensions is interfering. Disable extensions one by one to isolate the culprit. Common offenders: uBlock Origin custom filters, Privacy Badger, Ghostery, and any extension that modifies page CSS.

If incognito also fails, clear the full browser cache:

Chrome → Settings → Privacy and Security → Delete browsing data
Select "Cookies and other site data" + "Cached images and files"
Time range: Last 7 days (or All time if the issue persists)

Safari

Safari’s Intelligent Tracking Prevention can aggressively block Gemini’s session cookies. Try:
– Safari → Settings → Privacy → uncheck “Prevent cross-site tracking” temporarily.
– Safari → Settings → Advanced → check “Show Develop menu” → Develop → Empty Caches.

Mobile app (Android)

• Force stop the Gemini app: Settings → Apps → Gemini → Force Stop.
• Clear app cache (not data, unless necessary): Settings → Apps → Gemini → Storage → Clear Cache.
• Check for app updates in the Play Store.

Mobile app (iOS)

• Close the app from the app switcher entirely, then reopen.
• If that fails: delete and reinstall the app. iOS doesn’t expose a “clear cache” option for individual apps.

Region, Permissions, and Feature Availability

Region restrictions:
Gemini is not available in all countries. If you’re traveling or using a VPN, you may hit a region block even if the service works at home. Disconnect your VPN and try again — or switch your VPN to a supported region.

Google does not publish a single comprehensive list of supported countries for every Gemini feature. The Gemini help center lists general availability by region.

Google Workspace restrictions:
– Gemini for Workspace requires the admin to enable the feature at the organizational unit level.
– Some Workspace plans include Gemini; others require an add-on license.
– If you’re on a Workspace account and see “Gemini isn’t available,” contact your Workspace admin — not Google support.

Age restrictions:
Google accounts for users under 18 may have restricted access to Gemini, depending on region and account settings.

Feature-specific availability:
Not all Gemini capabilities launch simultaneously everywhere. Image generation, code execution, file uploads, and Gems may each have different availability timelines. A feature working for someone else doesn’t mean it’s rolled out to your account yet.

API and Developer Environment Fixes

Gemini API (Google AI Studio / REST)

Verify your API key works:

$ curl "https://generativelanguage.googleapis.com/v1beta/models?key=YOUR_API_KEY"
# Should return a JSON list of available models
# If you get 403: key is invalid, revoked, or billing isn't enabled
# If you get 429: you've hit your rate limit

Common API failure causes:

• Billing not enabled. The Gemini API free tier has request limits. If you exceed them, you need billing enabled on your Google Cloud project. The API returns 429 without a clear “enable billing” message.
• Wrong model name. Model identifiers change between versions. gemini-pro may be deprecated in favor of a newer version string. Check the Gemini API models documentation for current model names.
• Region mismatch. If using Vertex AI endpoints, ensure the region in your endpoint URL matches the region where Gemini models are deployed in your project.

Gemini Code Assist (VS Code / JetBrains)

1. Open the extension output log: in VS Code, open the Output panel (Ctrl + Shift + U) and select the Gemini Code Assist channel.
2. Look for authentication errors. If you see “token expired” or “auth failed,” sign out and re-authenticate through the extension’s account picker.
3. Check that your Cloud project has the Gemini Code Assist API enabled. The extension won’t work if the API isn’t active in the project linked to your account.
4. Verify your network allows outbound HTTPS to *.googleapis.com. Corporate firewalls and proxy servers commonly block these endpoints.

Network and Firewall Issues (All Platforms)

If Gemini fails on your work network but works on your phone’s mobile data:

• Your corporate firewall or proxy may block WebSocket connections to Google’s servers.
• DNS filtering (common with Pi-hole, NextDNS, or corporate DNS) may block Gemini-related domains.
• Try setting your DNS to 8.8.8.8 or 1.1.1.1 temporarily to rule out DNS-level blocks.

If It Still Fails

If none of the above steps resolve the issue:

1. Capture the exact error. Screenshot the error message, note the HTTP status code (for API), or copy the browser console output (F12 → Console tab). Vague reports like “it doesn’t work” get vague support responses.
2. Try a completely different device. If Gemini fails on your laptop, try your phone (or vice versa) on a different network. This definitively separates account issues from device/network issues.
3. Check community reports. Search for the specific error on the Google Gemini community forum or Reddit’s r/Bard and r/GoogleGeminiAI subreddits. If others report the same issue, it’s likely server-side.
4. Contact Google support. For Workspace accounts, your admin can file a support case. For personal accounts, use the feedback button (thumbs down icon) in the Gemini interface and the “Send feedback” option in the hamburger menu.
5. Wait and retry. Some Gemini issues are transient — model overload during peak hours, gradual rollouts that temporarily break, or backend deployments. If the problem appeared suddenly with no changes on your end, retrying after 30-60 minutes often resolves it.

FAQ