# Bug report: Antigravity server crashed unexpectedly

**URL:** <https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277>\
**Category:** Google Antigravity\
**Tags:** bug\
**Created:** [March 3, 2026, 11:27am UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277 "2026-03-03T11:27:08Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![wpa-hooligan](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/wpa-hooligan/32/100135_2.png) [@wpa-hooligan](https://discuss.ai.google.dev/u/wpa-hooligan)\
**Post date:** [March 3, 2026, 11:27am UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/1 "2026-03-03T11:27:08Z")

</div>

Hello, I could not make this bug report using the antigravity bug report feature because I got an error “An error occured while submitting your bug report”. So I’m putting it here.

I recently updated my antigravity version to Version: 1.19.6-1772152296 which should be the latest version as of this bug report.

Most of the time when I start the app I am spammed by a ton of error messages “Antigravity server crashed unexpectedly” and “Client gravity: connection to server is erroring”. If I click “go to output” I see this for each:

[Error - 6:19:31 AM] Stopping server failed  
Message: Cannot call write after a stream was destroyed  
Code: -32099  
[Error - 6:19:31 AM] Stopping server failed  
Message: Cannot call write after a stream was destroyed  
Code: -32099

[Info - 6:23:57 AM] Connection to server got closed. Server will restart.  
true  
[Error - 6:23:57 AM] antigravity client: couldn’t create connection to server.  
Error: connect ECONNREFUSED 127.0.0.1:39289  
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)  
[Error - 6:23:57 AM] Restarting server failed  
Error: connect ECONNREFUSED 127.0.0.1:39289  
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)

The AI features of the app still work just fine including the sidebar chat panel. This is mostly a visual distraction since I can’t get the errors to go away (eventually they stop after 5-10 minutes)

---

<div class="post-metadata">

**Author:** ![guitarfire](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/guitarfire/32/96045_2.png) [@guitarfire](https://discuss.ai.google.dev/u/guitarfire)\
**Post date:** [March 3, 2026, 11:32am UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/2 "2026-03-03T11:32:13Z")

</div>

I just started having a connection problem, maybe the server is down or is saturated.

---

<div class="post-metadata">

**Author:** ![wpa-hooligan](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/wpa-hooligan/32/100135_2.png) [@wpa-hooligan](https://discuss.ai.google.dev/u/wpa-hooligan)\
**Post date:** [March 3, 2026, 11:43am UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/3 "2026-03-03T11:43:19Z")

</div>

Maybe, but in that case why would the AI features still work? Also, I see this every time I open the app regardless of time of day.

---

<div class="post-metadata">

**Author:** ![Lucaso](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/lucaso/32/87382_2.png) [@Lucaso](https://discuss.ai.google.dev/u/Lucaso)\
**Post date:** [March 3, 2026, 12:14pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/4 "2026-03-03T12:14:17Z")

</div>

Im getting error for every prompt what i ask to agent. “Error - Our servers are experiencing high traffic right now…” Last month I paid for it.. Claude or Codex are more faster and more reliable.

---

<div class="post-metadata">

**Author:** ![guitarfire](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/guitarfire/32/96045_2.png) [@guitarfire](https://discuss.ai.google.dev/u/guitarfire)\
**Post date:** [March 3, 2026, 12:15pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/5 "2026-03-03T12:15:46Z")

</div>

Did you connect Codex into Antigravity? Is this easy to do?

---

<div class="post-metadata">

**Author:** ![guitarfire](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/guitarfire/32/96045_2.png) [@guitarfire](https://discuss.ai.google.dev/u/guitarfire)\
**Post date:** [March 3, 2026, 12:18pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/6 "2026-03-03T12:18:36Z")

</div>

I recommend uninstalling and downloading the latest antigravity version from the website. I had some problems updating this version, so I had to uninstall and install again.

---

<div class="post-metadata">

**Author:** ![Lucaso](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/lucaso/32/87382_2.png) [@Lucaso](https://discuss.ai.google.dev/u/Lucaso)\
**Post date:** [March 3, 2026, 12:31pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/7 "2026-03-03T12:31:57Z")

</div>

Yes, Codex work fine in antigravity.. Its 3x more faster and reliable. Just install official Codex from extension. It works fine.

---

<div class="post-metadata">

**Author:** ![guitarfire](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/guitarfire/32/96045_2.png) [@guitarfire](https://discuss.ai.google.dev/u/guitarfire)\
**Post date:** [March 3, 2026, 12:44pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/8 "2026-03-03T12:44:28Z")

</div>

Okay, I will find the best way to install it.

---

<div class="post-metadata">

**Author:** ![wpa-hooligan](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/wpa-hooligan/32/100135_2.png) [@wpa-hooligan](https://discuss.ai.google.dev/u/wpa-hooligan)\
**Post date:** [March 3, 2026, 4:28pm UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/9 "2026-03-03T16:28:48Z")

</div>

I uninstalled and reinstalled antigravity and it’s still happening ☹

---

<div class="post-metadata">

**Author:** ![chunduriv](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@chunduriv](https://discuss.ai.google.dev/u/chunduriv)\
**Post date:** [March 4, 2026, 1:50am UTC](https://discuss.ai.google.dev/t/bug-report-antigravity-server-crashed-unexpectedly/128277/10 "2026-03-04T01:50:56Z")

</div>

Hi @wpa-hooligan,

Welcome to the Forum,

A refused local loopback (127.0.0.1) connection may usually caused by following issues:

- Your strict Antivirus may be blocking the Antigravity background server from executing. You can temporarily disable your Antivirus or whitelist the Antigravity executable
- A server process may be stuck from a previous session, so terminate any lingering Antigravity background processes using the Task Manager
