# Google antigravity issue

**URL:** <https://discuss.ai.google.dev/t/google-antigravity-issue/185892>\
**Category:** Google Antigravity\
**Tags:** bug\
**Created:** [September 29, 2026, 2:48am UTC](https://discuss.ai.google.dev/t/google-antigravity-issue/185892 "2026-09-29T02:48:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anamika\_sharma](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/anamika_sharma/32/153591_2.png) [@Anamika\_sharma](https://discuss.ai.google.dev/u/Anamika_sharma)\
**Post date:** [September 29, 2026, 2:48am UTC](https://discuss.ai.google.dev/t/google-antigravity-issue/185892/1 "2026-09-29T02:48:10Z")

</div>

Subject: Antigravity Windows TLS certificate validation failure – OAuth token exchange and agent execution

I am experiencing a persistent TLS certificate verification failure in Google Antigravity IDE on Windows 11. The same issue occurs in Antigravity’s standalone installer and VS Code integration.

OAuth error: Post [https://oauth2.googleapis.com/token:](https://oauth2.googleapis.com/token:) tls: failed to verify certificate: x509: certificate signed by unknown authority.

Agent error: Get [https://daily-cloudcode-pa.googleapis.com/v1internal/buildWithGooglePlugins?page\_size=1000:](https://daily-cloudcode-pa.googleapis.com/v1internal/buildWithGooglePlugins?page_size=1000:) tls: failed to verify certificate: x509: certificate signed by unknown authority.

Windows curl.exe using Schannel successfully establishes TLS to [oauth2.googleapis.com](http://oauth2.googleapis.com) and receives HTTP 404, as expected for a GET request without an OAuth payload. Windows proxy settings show direct access, and no proxy environment variables are configured.

The browser certificate viewer showed [upload.video.google.com](http://upload.video.google.com) while accessing [oauth2.googleapis.com](http://oauth2.googleapis.com). Please investigate the certificate hostname mismatch and whether Antigravity’s bundled Go/Electron networking stack is using a different root CA store or rejecting the certificate chain.

The issue persists after Windows updates, reinstalling Antigravity, clearing application caches, trying different versions, and resetting network settings. Please escalate this to the Antigravity authentication/networking engineering team. Please advise which diagnostic logs and certificate-chain details are required.

---

<div class="post-metadata">

**Author:** ![Rebbanpalli\_Naveen](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/rebbanpalli_naveen/32/120945_2.png) [@Rebbanpalli\_Naveen](https://discuss.ai.google.dev/u/Rebbanpalli_Naveen)\
**Post date:** [September 30, 2026, 3:12pm UTC](https://discuss.ai.google.dev/t/google-antigravity-issue/185892/2 "2026-09-30T15:12:49Z")

</div>

Hi @Anamika_sharma,

Welcome to the Forum.

Thank you for the detailed diagnostic notes. Here is what is happening with the `upload.video.google.com` certificate and the `x509: certificate signed by unknown authority` error on Windows 11, along with how to resolve it:

1. **Why the Browser Shows `upload.video.google.com` for `oauth2.googleapis.com`:**

2. **How to Resolve the `x509: certificate signed by unknown authority` Error on Windows 11:**

3. **Diagnostic Details (If the Issue Persists):** If the steps above do not resolve the issue, please reply with: