# \[BUG\] There was a network issue connecting to the server, please try again. again **URL:** \ **Category:** Google Antigravity\ **Tags:** bug\ **Created:** [June 22, 2026, 1:39am UTC](https://discuss.ai.google.dev/t/bug-there-was-a-network-issue-connecting-to-the-server-please-try-again-again/172121 "2026-06-22T01:39:32Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Wingray\_SHU](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/wingray_shu/32/57540_2.png) [@Wingray\_SHU](https://discuss.ai.google.dev/u/Wingray_SHU)\ **Post date:** [June 22, 2026, 1:39am UTC](https://discuss.ai.google.dev/t/bug-there-was-a-network-issue-connecting-to-the-server-please-try-again-again/172121/1 "2026-06-22T01:39:32Z")
Is it a recurring theme that monumental disruptions inevitably unfold upon the arrival of the weekend? Commencing approximately twelve hours ago, my sessions began experiencing the perennial `Unknown: There was a network issue connecting to the server, please try again.` error, compounded by persistent timeout failures. At first, I chalked this up to yet another routine server degradation under peak loads. However, the underlying malaise appears far more systemic; indeed, even `https://translate.google.com/` is currently down (albeit confined to the web interface, as the translation engine itself remains functional). Furthermore, a substantial portion of cached images across this forum have failed to render, evocative of a sudden server rollback. Concurrently, another symptom has manifested: the **Quota** displayed within the IDE remains entirely static, showing no signs of depletion or replenishment… Trajectory ID: 0610fe02-5c6c-4c4b-b850-c2e0b1a27… Error: agent executor error: request failed: Post “[https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse](https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse)”: dial tcp 216.239.34.223:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.: request failed: Post “[https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse](https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse)”: dial tcp 216.239.34.223:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. (1) attached stack trace – stack trace: | google3/third\_party/gemini\_coder/framework/executor/agentexecutor/agentexecutor.(\*AgentExecutor).Run | third\_party/gemini\_coder/framework/executor/agentexecutor/agentexecutor.go:339 | […repeated from below…] Wraps: (2) agent executor error Wraps: (3) tags: map[stream\_receive\_count:0 streaming\_duration:0s] Wraps: (4) attached stack trace – stack trace: | google3/third\_party/gemini\_coder/framework/generator/generator.(\*streamResponseHandler).processStream | third\_party/gemini\_coder/framework/generator/stream\_handler.go:329 | google3/third\_party/gemini\_coder/framework/generator/generator.(\*PlannerGenerator).attemptGenerate | third\_party/gemini\_coder/framework/generator/planner\_generator.go:451 | google3/third\_party/gemini\_coder/framework/generator/generator.(\*PlannerGenerator).generateWithAPIRetry | third\_party/gemini\_coder/framework/generator/planner\_generator.go:286 | google3/third\_party/gemini\_coder/framework/generator/generator.(\*PlannerGenerator).generateWithModelOutputRetry | third\_party/gemini\_coder/framework/generator/planner\_generator.go:148 | google3/third\_party/gemini\_coder/framework/generator/generator.(\*PlannerGenerator).Generate | third\_party/gemini\_coder/framework/generator/planner\_generator.go:91 | google3/third\_party/gemini\_coder/framework/executor/executor.(\*Executor).executeLoop | third\_party/gemini\_coder/framework/executor/executor.go:369 | google3/third\_party/gemini\_coder/framework/executor/executor.(\*Executor).Execute | third\_party/gemini\_coder/framework/executor/executor.go:288 | google3/third\_party/gemini\_coder/framework/executor/agentexecutor/agentexecutor.(\*AgentExecutor).Run | third\_party/gemini\_coder/framework/executor/agentexecutor/agentexecutor.go:305 | google3/third\_party/jetski/cortex/cortex.(\*CascadeManager).executeHelper.func1 | third\_party/jetski/cortex/cascade\_manager.go:1732 | google3/third\_party/jetski/cortex/utils/background.(\*Pool).Go.func2 | third\_party/jetski/cortex/utils/background.go:121 | google3/go/context/detach.Go.func1 | go/context/detach.go:247 | runtime.goexit | third\_party/go/gc/src/runtime/asm\_amd64.s:1774 Wraps: (5) request failed: Post “[https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse](https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse)”: dial tcp 216.239.34.223:443: bind: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Wraps: (6) request failed Wraps: (7) Post “[https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse](https://daily-cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse)” Wraps: (8) dial tcp 216.239.34.223:443 Wraps: (9) bind Wraps: (10) An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Error types: (1) \*withstack.withStack (2) \*errutil.withPrefix (3) \*go\_utils.withTags (4) \*withstack.withStack (5) \*errutil.withPrefix (6) \*fmt.wrapError (7) \*url.Error (8) \*net.OpError (9) \*os.SyscallError (10) syscall.Errno ---
**Author:** ![Siddharth\_Naik](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@Siddharth\_Naik](https://discuss.ai.google.dev/u/Siddharth_Naik)\ **Post date:** [July 14, 2026, 1:46pm UTC](https://discuss.ai.google.dev/t/bug-there-was-a-network-issue-connecting-to-the-server-please-try-again-again/172121/2 "2026-07-14T13:46:27Z")
It is possible that this was a transient issue. However, if you continue to experience this unexpected behavior, please let us know! To help us investigate if it does happen again, it would be incredibly helpful if you could provide a few additional details: - The specific platform and version you are using - The specific model and sample prompts you are testing with