Field note
Gemini Not Working: Error 1076 and 1099 Fixes
Google does not publish a meaning for Gemini error numbers such as 1076 and 1099, so treat the number as a label for your ticket and work through account, browser, network and status checks in order.
Google does not publish a meaning for Gemini error numbers such as 1076 and 1099, so treat the number as a label for your ticket and work through account, browser, network and status checks in order.
What the number does and does not tell you
At the time of writing there is no Gemini Apps Help article that defines error 1076 or error 1099, and a search of the help centre returns nothing for either. Anyone who tells you a definite cause is guessing.
What Google does document is the wording around failures. "Something went wrong" while signing in means the account cannot access the app at the moment, which Google says can be due to location, age or account type among other reasons. "Can't access this service" means the account is not eligible: it needs to be a personal account, or a work or school account where the administrator has enabled Gemini. Usage limits produce their own message and tell you when the limit refreshes. Gemini in Chrome is unavailable in Incognito mode and in unsupported regions.
So record what you can observe: the number, the exact message, the time, the account type (personal or Workspace), the surface (gemini.google.com, the mobile app, the Chrome side panel or the Workspace side panel) and what you were doing, such as uploading a file, calling a connected app, starting Live or continuing a long chat. That record is worth more than the number.
Likely causes, most common first
- Account or entitlement. A work account without Gemini enabled by the administrator, a work account whose user is not marked as 18 or over, or a personal account that fails an age or region check.
- Session or browser. A stale sign-in, an extension that alters requests, or a browser Google does not list as supported. The supported browsers at the time of writing are Chrome, Safari, Firefox, Opera and Edge.
- Network. A corporate proxy, TLS inspection or web filter blocking one of the Google domains Gemini needs. A VPN can also make the location look unsupported. The Workspace admin help has a page on Gemini app firewall settings for this reason.
- Capacity or limits. Google says limits may change without notice, including because of capacity, and that users without a paid plan may be limited before subscribers when capacity is short.
- A Google incident. Check the Google Workspace status dashboard before spending an hour on local fixes.
- One feature, not the product. File upload, a connected app or Live can fail while plain chat works.
Step-by-step fix
- Write down the details listed above, then take a screenshot of the message.
- Sign out and sign back in on gemini.google.com in a normal window with only the affected account.
- Open an Incognito window and sign in with the same account. The web app works there; the Chrome side panel does not, so use the web app for this test. If it now works, an extension or cached state was the problem.
- Try a different network, such as a phone hotspot. If it works there, the fault is in the office network path.
- Try a different browser or device on the same network.
- Check Settings, then Usage Limits, in the Gemini app to see whether you are close to or at a limit.
- Check the status dashboard for a current Gemini or Workspace incident.
- If a specific feature fails, start a new chat and send a plain text prompt. If that works, report the feature rather than the product.
Stop when one test isolates the cause. Do not keep refreshing.
What IT or the administrator should check
- In the Workspace Admin console: the Gemini app is on for the user's organisational unit, access to Workspace services in the Gemini app is set as intended, the edition qualifies, and the user's age setting is correct.
- Proxy and web-filter logs for blocked requests to Google domains at the time of the error, then compare against Google's firewall guidance for the Gemini app.
- Whether the user is signed into a personal Google account inside a managed browser. That is a policy problem as well as a support problem.
- Do not "fix" an entitlement failure by asking staff to use a personal account for work.
The same discipline for a different product is in ChatGPT not working on a work network and Claude not working: status versus capacity.
When to escalate to Google
Escalate when the failure reproduces on two networks and two browsers, the status dashboard is clear, and the administrator has confirmed the settings. Personal account users report it in the Gemini app under Settings and help, then Send feedback, with the screenshot attached. Work accounts go through the organisation's Workspace administrator, who can open a support case. Include the error number, the exact wording, the time and the surface, because that is what a support engineer can correlate with logs.