Login successful, but all new chats return 400: User location is not supported

Google Antigravity
1

Antigravity Login Successful, but Model Request Rejected by Region Check

Request: Please assist in verifying account region eligibility and the geolocation classification of the outbound egress IP to confirm the reason for rejection.

Environment & Reproduction

  • Date: 2026-09-30; local timezone: Asia/Shanghai (UTC+8).
  • System: macOS; Antigravity version: 2.18.1.
  • User report: The Terms of Service page for the Google account used to log in indicates the country/region as Japan.
  • Google login succeeded after using the local FlClash HTTP proxy (127.0.0.1:7890).
  • FlClash connection screenshots show daily-cloudcode-pa.googleapis.com:443 connecting via the selected node in the “Node List” with bidirectional data. The node name is labeled as the United States; the actual egress location and Google’s classification of this IP have not yet been verified.
  • The issue persisted after switching nodes; completely exiting and restarting Antigravity, creating a new conversation, and sending “Hello” still failed.

Most Recent Error

  • Background process restarted: 2026-09-30 09:52:16 (local log time).
  • New conversation message sent: 09:53:09.
  • Model execution failed: 09:53:11.
  • UI Error ID: 1ac7f16e-9936-461d-ac2d-701163b4f5d1-1.
  • Log trajectory_id: 1ac7f16e-9936-461d-ac2d-701163b4f..
agent executor error: generating and executing: FAILED_PRECONDITION (code 400): User location is not supported for the API use.

Conversation title generation at 09:53:14 also returned the same region error.

Confirmed and Pending Verification

  • The current failure is a server-side region rejection, which differs from the initial TCP connection timeout on the OAuth token endpoint.
  • Restarting and opening new conversations did not resolve the error.
  • Based on current evidence alone, it is not possible to determine whether this is due to egress IP geo-classification, account eligibility determination, or other server-side region checks.
  • Support staff are requested to investigate the cause based on the error ID and timestamp, and to advise on any further diagnostic information needed.

This document does not contain passwords, access tokens, cookies, proxy subscription links, or full raw logs; it has not been shared with any third party.

2

Hi @rick_tang,

Thanks for the detailed report! The issue here is definitely the proxy you’re using.

Even though your account is set to Japan and your proxy is pointing to the US, Google’s API actively blocks known VPN and datacenter IPs to prevent abuse. That’s why you can log in fine (the auth servers are less strict), but as soon as you try to actually send a prompt, the API backend flags your proxy’s IP and throws the 400 error.

Since this is a network-level block, there’s no setting in the Antigravity that can fix it. You’ll need to either use a direct connection without a proxy.

Let me know the update!