Persistent "An internal error has occurred" / HTTP 403 Forbidden on Brave - Requires Refresh / Regenerate

Google AI Studio
, ,
1

Hi Google AI Studio Team & Community,

I am experiencing a persistent issue in Google AI Studio on Brave where prompts repeatedly fail with:

> “An internal error has occurred” (Failed to generate content: permission denied)

### Behavior & Details:

  • **Environment:** Brave 1.93.129 Chromium: 151.0.7922.71 (64-bit) / Windows 10 22H2
  • **Tested on Firefox:** Does NOT occur in Firefox (works fine).
  • **Tested on Brave:** Occurs repeatedly in Brave with both **Shields ON** and **Shields OFF**.
  • **Workaround:** Clicking “Regenerate” sometimes works. If not, refreshing the page (via normal refresh or Ctrl+F5) temporarily clears the issue until it happens again.

Developer Tools shows HTTP 403 Forbidden on RPC POST requests to:

https://alkalimakersuite-pa.clients6.google.com/$rpc/google.internal.alkali.applications.makersuite.v1.MakerSuiteService/GenerateContent

with error body: [,[7,“The caller does not have permission”]].

0w9586q
0w9586q785×374 12.9 KB

Please look into this Web UI session token lifecycle / refresh issue in Brave. Thank you!

2

Hi,
Getting a 403 API error response and / or seeing “Unavailable” next to your project in AI audio indicates a flag has been placed on your account. To proceed:

  1. If you’re on the free tier with no billing attached, you should consider setting up billing. In most cases this is enough to clear any flag on your account. Please note this will mean you lose your free tier quota. You should also see a banner in AI studio prompting you to set up billing.

  2. If you are on a paid tier, check for banners / error callouts in the AI Studio Projects page & the Billing page. Mostly these flags cause visible banners or other errors on these pages with concrete next steps / appeal links. You can also check the email address associated with your project for information on next steps.

3

You’re confidently wrong. Re-read the post, sometimes it works without this error. It doesn’t happen at all on Firefox. There’s no flag, don’t make BS up.