antigravity is always Access denied

[pixel4696]

it seems that antigravity is always Access denied today. the same account works nicely yesterday

[diegosouzapw]

Hi @pixel4696. "Access denied" alone doesn't tell us enough to say where it comes from. Could you send:

1. The full error as OmniRoute reports it: the status code and message, from the response or from app.log (~/.omniroute/logs/application/app.log). Please redact tokens and emails.
2. Your OmniRoute version (omniroute --version, or the image digest if you use Docker).
3. Whether the same account works in the Antigravity app itself today.
4. Whether every model fails, or only some of them. If you have more than one account connected, whether they all fail.

The third point matters most. If Antigravity itself also refuses the account, the restriction is on Google's side and not in OmniRoute's routing.

[pixel4696]

[403]: Antigravity upstream error (403): Verify your account to continue.

i am running docker :next tag today

the same account works in Antigravity app

all of the model fails

[diegosouzapw]

Thanks, @pixel4696. That message settles where it comes from. Verify your account to continue is Google's response, not OmniRoute's. OmniRoute passes it through and treats it as an account-level block signal (ACCOUNT_DEACTIVATED_SIGNALS in open-sse/services/accountFallback.ts), which is why every model fails at once.

The account still working in the Antigravity app on your own machine suggests Google is challenging this specific access path (where the requests come from, or how they look), not that the account is closed. Either way, nothing in OmniRoute's routing can clear it, and retrying won't get past it.

What usually helps:

1. Sign in to that Google account in a normal browser and complete whatever verification Google shows (phone, security check), then reconnect the account in OmniRoute.
2. If OmniRoute runs on a VPS or in a data center, that network is the likely trigger. Try the same account from a machine on your home network, or route that connection through a residential proxy (the per-connection proxy setting).

If the challenge keeps coming back after you've verified, stop routing that account through OmniRoute for a while instead of retrying.