Start here: save your draft, open a fresh chat and send a short text-only question. If error 1155 persists, sign into the same account in a private window. Text that works until you attach a file points toward the upload step; failure in just one browser points toward that browser’s environment. Change one condition at a time.
What is Gemini error 1155?
Something went wrong (1155) is an error users have reported in Gemini Apps. Our search did not find an official Google definition of its exact cause or a dedicated fix announcement. A Google Help Community report dates back to June 13, 2026, so an October keyword-discovery date is not the date this error first appeared. Read the original discussion.
A product expert in that thread suggested communication, VPN and session issues, with private-window, network and site-data tests. These are community troubleshooting suggestions, not an official error-code specification. The number alone does not establish an account ban, a failed subscription or server overload.
Isolate the failure before clearing anything
This is our diagnostic sequence, not a guaranteed fix. Keep the account and a harmless short question constant, such as “Explain a token in one sentence.” Write down each result. Changing the network, account and browser simultaneously makes it difficult to know which change helped.
| What you observe | Investigate first | Next action |
|---|---|---|
| Old chat fails; new chat works | The conversation or original request | Add back only the necessary context, in small parts |
| Regular window fails; private window works | Extensions, site data or session state | Test relevant extensions individually |
| Text works; attachments fail | Uploading or reading a file | Try one small file before the original attachment |
| The same account works on another network | Network routing or filtering | Check the VPN, proxy or managed-network rules |
| Multiple devices and networks fail | An account or service issue remains possible | Record the tests, wait and send feedback |
Six steps to troubleshoot Something went wrong (1155)
- Save the draft and test a fresh chat. Copy unsent work somewhere safe. Remove attachments, links and long background text. If a short question succeeds, divide the original request into smaller steps to identify the trigger. You do not need to delete your chat history first.
- Try a private window. Sign into the same account and repeat the same question. If it works, return to your regular window and test relevant content blockers, privacy tools and script-modifying extensions one at a time. Private mode changes more than one browser condition, so success does not prove an extension is the sole cause.
- Compare a trusted network. If you use a VPN or proxy, briefly pause it only where direct Gemini access is permitted, or try a trusted mobile hotspot. Ask an administrator to review work or school filtering rules. Treat this as a connectivity test, not a way to bypass regional or account restrictions.
- Reset only the relevant site data. If private mode works but your normal browser repeatedly fails, make sure you can sign back in, then clear cache and site data for
gemini.google.comusing your browser settings. This can sign you out and remove unsaved local state. Clearing every website’s data is unnecessary. - Separate attachment errors from generation errors. Try one small supported file. If that works, check the original format, size, count and whether the file opens locally. Test a single page of a scanned PDF or a short video segment before the full item. Avoid repeatedly uploading the same large file.
- Stop repeated retries when the minimal test fails everywhere. If the same simple request fails across browsers and trusted networks, record the time, timezone and results, then retry later or send feedback. That pattern makes an account or service issue more plausible, but does not identify a definitive cause.
Private-window, network and site-data suggestions draw on the 1155 community reply. The test sequence and interpretation above are Token King’s synthesis, not results from a controlled reproduction.
Check file limits if uploads trigger the error
Google’s current help page lists up to 10 files per prompt, subject to availability; supported non-video files up to 100 MB each; and videos up to 2 GB each. Video duration and other usage limits depend on the plan. Staying below a size limit does not guarantee successful parsing. Google’s upload documentation.
Use this progression: text without files → one small file → the original file → additional attachments. It distinguishes a general generation failure from a file-specific trigger. If Gemini explicitly reports an upload quota or storage limit, investigate that message rather than assuming it explains every 1155 error.
Using the Gemini API? Diagnose the API response instead
The web app’s 1155 message is not the same diagnostic system as an API HTTP status. Record the status, error type and any available request identifier. Google recommends exponential backoff for retryable responses such as 429 RESOURCE_EXHAUSTED and 503 UNAVAILABLE; official SDKs already retry some transient failures. Gemini API troubleshooting.
Check whether the SDK retries before adding your own retry loop, and bound attempts and total waiting time. Browser cache changes cannot repair your server’s API parameters, quota or backend failure.
Send a reproducible report if it still fails
On the Gemini website, choose Settings & help, then Send feedback. Google says feedback can include the associated conversation and attachments. Review the material and remove information you should not share. Google’s feedback instructions.
Error: Something went wrong (1155)
Time and timezone:
Device / operating system / browser version:
Account type: personal / work / school (no password needed)
Minimal reproduction: does a new text-only chat fail?
Private-window result:
Second network or device result:
Attachments: format, size and count (no sensitive originals)Frequently asked questions
Does a VPN cause Gemini 1155?
Not necessarily. Recovery after pausing it is evidence about the current network route. If nothing changes, continue testing the browser, attachments and account environment. One community explanation is not a universal diagnosis.
Should I buy a higher plan?
Error 1155 alone is not a reason to upgrade. Check for an explicit quota message and run the text-only and cross-environment tests first. Paid accounts can also encounter session or service failures.
Will switching AI platforms fix it?
Another platform may let you continue the task, but it will not repair your Google account or Gemini web app. Check the model, privacy terms and cost before switching. Do not give a supposed “repair site” your password, verification code or API key.