SSL certificate error since Antigravity 2.18.1, still present in 2.19.1

Google Antigravity
1

Hi,

Since updating to Antigravity 2.18.1, I have been unable to properly connect to the model after reconnecting my Google account.

The error is related to SSL/TLS certificate verification. The error we identified was:

unable to verify the first certificate

with the related x509 / certificate verification error.

I expected this to be fixed in the next update, but unfortunately the same issue is still present in Antigravity 2.19.1.

For now, I have had to remain on an older version where everything works correctly. This is quite frustrating because it means I cannot use the new features and improvements added in the newer releases.

I also tried launching Antigravity with:

--ignore-certificate-errors

but this did not resolve the issue.

This seems particularly strange because the same environment worked correctly before 2.18.1, and the problem appeared after that update.

Could the team please investigate the certificate/SSL handling introduced or changed in 2.18.1?

I can provide the full error output and logs if needed.

Thank you.

2

Hi @Amlaach,

Welcome to the Forum and thank you for reporting this.

Please try the following workarounds :

  • Check for Proxy, VPN, or Antivirus HTTPS/SSL Scanning: The unable to verify the first certificate / x509 error usually occurs when a VPN, corporate proxy, firewall, or antivirus Web/HTTPS scanner intercepts traffic and replaces or strips intermediate certificates in the TLS chain. Please try connecting directly with any VPN or proxy disabled, or add an HTTPS inspection exclusion for *.googleapis.com and oauth2.googleapis.com in your security software.
  • Clear Cached Auth State & Re-Authenticate: After disabling any proxy or HTTPS scanner, sign out, close Antigravity 2.0 (v2.19.1) completely, clear your local session cache (%APPDATA%\Antigravity and %USERPROFILE%\.gemini on Windows, ~/Library/Application Support/Antigravity and ~/.gemini on macOS, or ~/.config/Antigravity and ~/.gemini on Linux), and sign back in.

If the error still persists after trying these steps, please reply with your operating system, the last version before 2.18.1 that worked for you, and attach either your diagnostic logs in a .txt file or an error screenshot.

3

Thanks for the suggestions.

Unfortunately, I cannot disable the Netspark/Rimon filtering on this device, so I’m unable to perform a test with the filtering completely disabled.

However, the important point is that the exact same filtering environment worked correctly with Antigravity before version 2.18.1. The SSL error appeared after updating to 2.18.1, and it is still present in 2.19.1.

So it seems there may have been a change in certificate/SSL handling between the older version and 2.18.1 that affects environments using HTTPS inspection.

I can provide the diagnostic logs and the full error output from the affected version if that would help investigate this further.

4

Thank you very much! It’s great that this issue was fixed in version 2.21.0, released today, at least on my end.

I really appreciate it. Thank you!