Repeated Antigravity error FAILED_PRECONDITION: User location

Since today I get repeated error messages for “FAILED_PRECONDITION: User location” in both Antigravity 2.0 CLI and the Remote Control function. I get these on both by home PC and on my VPS. The failures are intermittent, but more than 50%+ of the requests fail due to this error. I am located in a supported country and have been using Antigravity for several weeks without issue. I have a paid AI Pro subscription that includes Antigravity.

Full error: ⚠ FAILED_PRECONDITION (code 400): User location is not supported for the API use.
Error ID: 6fc077ab-5af8-4d10-94e7-994fce934f1c-19

There are no existing service health issues. Is this a known issue? It makes Agy unusable.

Hi @darses,

Welcome to the Forum,

When you get that FAILED_PRECONDITION (code 400) error even though you are in a supported region, it usually means systems are misinterpreting your specific ISP’s routing path or IP address. Also, if you happen to be using a proxy, the connection can sometimes bypass the standard HTTP_PROXY environment variables, revealing an origin IP that trips the region block.

Could you please try the following troubleshooting steps?

1. Disable IPv6 on Your Network Adapter When ISPs rotate IPv6 prefixes, the new block can sometimes be mistakenly flagged as out-of-region.

  • Windows: Open Control Panel > Network Connections > Right-click your Wi-Fi/Ethernet > Properties > Uncheck Internet Protocol Version 6 (TCP/IPv6) > Click OK.
  • macOS: Go to System Settings > Network > Your Connection > Details > TCP/IP > Set Configure IPv6 to Link-local only. Restart Antigravity and try again.

2. Disable VPNs, Proxies, or Private Relay

  • Turn off any active VPNs or corporate proxy clients.
  • On macOS, ensure iCloud Private Relay is toggled off under your Apple ID settings.

3. Test with a Mobile Data Hotspot

  • Connect your PC to your phone’s cellular hotspot. Check if Antigravity works on mobile data.

(Note: Please upgrade to the latest version of Antigravity)

Hi, thanks for reaching out.

I have already tried the first option (Disable IPv6) and the second option was never an issue as I do not use VPN’s or Proxies.

I will give the third option a try, but it seems this is not an issue on my end. Everything worked fine before today.

Hi,

I am experiencing the exact same issue.

Unfortunately, my experience with support has been very disappointing. Over the course of two weeks, I provided detailed logs, screenshots, and a clear breakdown of the problem. Despite this, I kept receiving the same generic questions in a loop, all of which had already been answered.

I repeatedly asked for the ticket to be escalated to a tier-2 or senior technical team, but received no response. In the end, rather than investigating and fixing the issue, support simply terminated my subscription (an AI Pro 5TB plan). According to them, I retain access until next May, but it will not be renewed and no refund was offered.

On top of that, even before the lockout, when I could still log in, I was inexplicably restricted to using only third-party models (Anthropic and OpenAI).

As a long-time user and advocate of Google products, it is genuinely disheartening to see such a decline in technical support quality.

Best of luck getting this sorted out.

Sorry to hear that. I will try to take some steps to figure this out, but given your experience and the many unanswered questions on this forum it looks like this is a known unsolved reliability issue on Google’s side. I could only wish I knew about this before I spent my money on a Google AI subscription.

At this point it appears that my home connection is working again, without resorting to a mobile data connection. The issue persist on the VPS running in a datacenter in the same country.