All Gemini models fail in Antigravity with 400

Google Antigravity
1

I’ve checked my T&C location and it says France. I’m not using any VPN

Trajectory ID: 501093af-dc32-4042-ad77-9c3183453..
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0x6033c5491e1e22..
Headers: {"Alt-Svc":["h3=":443"; ma=2592000,h3-29=":443"; ma=2592000"],"Content-Length":["140"],"Content-Type":["text/event-stream"],"Date":["Thu, 01 Oct 2026 09:42:50 GMT"],"Server":["ESF"],"Server-Timing":["gfet4t7; dur=1205"],"Vary":["Origin","X-Origin","Referer"],"X-Cloudaicompanion-Trace-Id":["6033c5491e1e2.."],"X-Content-Type-Options":["nosniff"],"X-Frame-Options":["SAMEORIGIN"],"X-Xss-Protection":["0"]}

{
"error": {
"code": 400,
"message": "User location is not supported for the API use.",
"status": "FAILED_PRECONDITION"
}
}

Is it related to the ISP?
curl -4 ``https://ifconfig.co/json
curl -6 ``https://ifconfig.co/json
{
"ip": "57.129.62.177",
"ip_decimal": 964771505,
"country": "France",
"country_iso": "FR",
"country_eu": true,
"latitude": 48.8582,
"longitude": 2.3387,
"time_zone": "Europe/Paris",
"asn": "AS16276",
"asn_org": "OVH SAS",
"user_agent": {
"product": "curl",
"version": "8.14.1",
"raw_value": "curl/8.14.1"
}
}{
"ip": "2001:41d0:701:1100::9392",
"ip_decimal": 42541823000225567360909371347992351634,
"country": "Germany",
"country_iso": "DE",
"country_eu": true,
"region_name": "Hesse",
"region_code": "HE",
"zip_code": "60313",
"city": "Frankfurt am Main",
"latitude": 50.1187,
"longitude": 8.6842,
"time_zone": "Europe/Berlin",
"asn": "AS16276",
"asn_org": "OVH SAS",
"hostname": "``vps-71145d8d.vps.ovh.net``",
"user_agent": {
"product": "curl",
"version": "8.14.1",
"raw_value": "curl/8.14.1"
}
}

2
3

I’m sorry that’s incredibly unhelpful. Of course I’ve asked AI. I’ve tried different computers, different networks, VPNs on and off and all of it doesn’t work. In any case, I should be able to use Antigravity from any combination of things I’ve tried, and I definitely shouldn’t have to enable some kind of root level IPV6 preference so that I can use an application even if that did work. Claude works fine. This is a bug and not user error.

4

Hi @jpopesculian,

Welcome to the Forum,

Based on the diagnostic output you provided, your traffic is routing through a cloud datacenter host (OVH Cloud VPS). Cloud datacenter IP ranges proxies and VPNs trigger these location policy blocks.

To resolve this issue, please try the following steps:

  • Please disconnect from any VPS/VPN tunnels and connect directly through your standard residential internet connection.

  • While you mentioned your T&C location is France, please ensure the country associated with your Google Account is correctly set at https://policies.google.com/terms.

  • Once on a residential network, open the Command Palette in Antigravity (Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS), select Antigravity: Reset Onboarding and log back in to refresh your connection.

5

Hi @chunduriv ,

Thanks for the reply. At least on Linux there’s no “Reset Onboarding” command. Also does that mean I can’t use Antigravity in my VPS?

Best,
Julian

6

Hi @chunduriv,
As there was no “Reset onboarding”, I deleted ~/.gemini, ~/.config/Antigravity, ~/.cache/antigravity and removed any logins from the GNOME keyring. I relogged in to Antigravity and the error persists:

Trajectory ID: c44c8036-c27d-44f5-a902-e0963b7…
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xd8b5e15c396d…
Headers: {“Alt-Svc”:[“h3=”:443"; ma=2592000,h3-29=“:443”; ma=2592000"],“Content-Length”:[“140”],“Content-Type”:[“text/event-stream”],“Date”:[“Mon, 05 Oct 2026 09:42:00 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=1090”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“d8b5e15c396de94”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 400,
“message”: “User location is not supported for the API use.”,
“status”: “FAILED_PRECONDITION”
}
}

I can confirm my IP addresses are indeed residential and my terms are labeled as France for the logged in account.

curl -4 https://ifconfig.co/json
curl -6 https://ifconfig.co/json
{
“ip”: “92.184.113.24”,
“ip_decimal”: 1555591448,
“country”: “France”,
“country_iso”: “FR”,
“country_eu”: true,
“latitude”: 48.8582,
“longitude”: 2.3387,
“time_zone”: “Europe/Paris”,
“asn”: “AS3215”,
“asn_org”: “Orange”,
“hostname”: “92-184-113-24.mobile.fr.orangecustomers.net”,
“user_agent”: {
“product”: “curl”,
“version”: “8.5.0”,
“raw_value”: “curl/8.5.0”
}
}{
“ip”: “2a01:cb1e:105c:bf3d:5acd:d323:5aed:88a9”,
“ip_decimal”: 55836887830883302642953417691063224489,
“country”: “France”,
“country_iso”: “FR”,
“country_eu”: true,
“latitude”: 48.8582,
“longitude”: 2.3387,
“time_zone”: “Europe/Paris”,
“asn”: “AS3215”,
“asn_org”: “Orange”,
“user_agent”: {
“product”: “curl”,
“version”: “8.5.0”,
“raw_value”: “curl/8.5.0”
}

7

I found a workaround that fixed this issue for me.

When Antigravity Desktop was returning:

FAILED_PRECONDITION: User location is not supported for the API use

I opened the Antigravity website, connected to my local Antigravity instance through Remote Control, and started a task from the web interface.

That remote task completed successfully. After that, the local Antigravity client was also able to generate Gemini responses normally again.

So the workaround is:

  1. Open the Antigravity web app.

  2. Connect to your local machine with Remote Control.

  3. Start and complete one Gemini task from the web interface.

  4. Return to the desktop client and try Gemini again.

In my case, this restored Gemini generation without reinstalling Antigravity, changing accounts, or modifying local files.

I cannot confirm yet why this works. It may trigger some session / eligibility / backend state refresh, but the important part is that Remote Control successfully restored local Gemini responses for me.

Would be useful if others with the same 400 error could test this and report whether it also works for them.