Gemini acting up? Before you panic, try these fixes first.
Gemini won’t connect or load
Problem: Connection failures or the app won’t open.
Fix: Test Gemini in a web browser first at gemini.google.com. Clear cache and cookies, disable VPNs or custom DNS, and make sure Google Play Services (on Android) and the Google app are up to date.
Chat history or conversations missing
Problem: Your sidebar looks empty or past conversations have disappeared.
Fix: This is sometimes a known backend issue rather than something on your end. Check Google’s Workspace status page; if it’s a known incident, your history typically returns once Google resolves it. If not, try logging out and back in.
Persistent error messages
Problem: Gemini Pro shows repeated errors, sometimes after working fine for hours.
Fix: Try a private/incognito window first — if it works there, a browser extension is the culprit. Otherwise clear cache and cookies, log out and back in fully, and start a fresh conversation, since a corrupted thread can sometimes be the cause.
Gemini Live mic or voice not working
Problem: Microphone isn’t responding or the connection drops during voice chat.
Fix: Check app permissions for microphone access, confirm a stable internet connection, and restart the app. If it persists across networks, it’s likely an app-level bug — try reinstalling.
Access blocked for work/school accounts
Problem: Gemini won’t work on a university or workplace Google account.
Fix: Test the same prompt on a personal Google account. If it works there, the issue is an administrative restriction — your organization’s IT admin will need to enable Gemini access.
Custom instructions (Gems) being ignored
Problem: Your custom Gem instructions aren’t being followed.
Fix: This usually comes down to instruction clarity and structure rather than a bug — be specific and avoid conflicting instructions within the same Gem.
Still not working?
Send detailed feedback directly from the app: tap the Help icon, then Send Feedback, and mention any troubleshooting you’ve already tried (cache clearing, account switching, etc.) to speed up the response.