codex - 💡(How to fix) Fix WebSocket transport reconnect loop when IPv6 is unavailable [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19525Fetched 2026-04-26 05:15:53
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.125.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.5

What platform is your computer?

OSVersion Linux Environment Server

What terminal emulator and version are you using (if applicable)?

VS Code

What issue are you seeing?

codex_ipv6_websocket_bug_report.md

What steps can reproduce the bug?

This happens when you use third party servers for relay of connection or even over VPN services that do not use IPv6 and prefer IPv4.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue is likely related to IPv6 WebSocket connectivity and can be mitigated by ensuring the use of IPv4 or configuring the environment to properly handle IPv6 connections.

Guidance

  • Verify that the third-party servers or VPN services used for relay connections support IPv6 and are properly configured.
  • Check the Codex CLI configuration to see if there are any options to force the use of IPv4 instead of IPv6.
  • Review the provided bug report (codex_ipv6_websocket_bug_report.md) for more detailed information on the issue.
  • Consider testing the connection without using third-party servers or VPN services to isolate the issue.

Notes

The provided information does not include enough technical details to pinpoint the exact cause of the issue, and the bug report is not accessible. Therefore, the suggestions are based on the limited information available.

Recommendation

Apply workaround: Use IPv4 instead of IPv6 for the connection, if possible, to avoid the WebSocket issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING