codex - 💡(How to fix) Fix Codex App Remote SSH times out on codex --version probe after successful SSH path probe

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…

Error Message

connection_state_changed error={"code":"connection-failed","message":"SSH: codex --version check timed out after 30000ms"}

Root Cause

This looks distinct from public-key/PAM authentication failures because manual public-key SSH succeeds, the app reaches the path probe, and codex_path_probe exits with code 0 before the timeout.

Code Example

SSH: codex --version check timed out after 30000ms

---

ssh <ssh-alias> "command -v codex; codex --version; codex -V"

---

/usr/local/bin/codex
codex-cli 0.130.0
codex-cli 0.130.0

---

ssh <ssh-alias> "codex app-server --help"

---

selected app-server transport hostId=<redacted>
sshHost=<redacted> sshPhase=connect sshPort=22
codex_path_probe code=0

---

app_server_connection.installed_codex_version_probe_failed errorMessage="SSH: codex --version check timed out after 30000ms" hostId=<redacted>
app_server_connection.transport_connect_failed errorMessage="SSH: codex --version check timed out after 30000ms" hostId=<redacted>
connection_state_changed error={"code":"connection-failed","message":"SSH: codex --version check timed out after 30000ms"}
RAW_BUFFERClick to expand / collapse

What happened

Codex App Remote SSH connects to a Linux host far enough to complete the SSH/path probe, but then fails during the installed Codex version probe. The app reports:

SSH: codex --version check timed out after 30000ms

Manual SSH from the same Windows client to the same SSH config alias returns immediately for the same checks.

Environment

  • Client: Codex App on Windows using Windows OpenSSH
  • Remote: Linux host
  • Remote Codex CLI: codex-cli 0.130.0
  • SSH config entry: concrete alias, public-key auth, no ProxyCommand/ProxyJump

Manual SSH checks that work

From the client shell:

ssh <ssh-alias> "command -v codex; codex --version; codex -V"

Output:

/usr/local/bin/codex
codex-cli 0.130.0
codex-cli 0.130.0

The remote app-server help path also exits successfully through SSH:

ssh <ssh-alias> "codex app-server --help"

The remote login-shell startup path was checked separately, and command -v codex resolves to /usr/local/bin/codex.

Codex App log pattern

The Codex App selects the intended SSH host and the SSH path probe succeeds:

selected app-server transport hostId=<redacted>
sshHost=<redacted> sshPhase=connect sshPort=22
codex_path_probe code=0

Then the version probe times out:

app_server_connection.installed_codex_version_probe_failed errorMessage="SSH: codex --version check timed out after 30000ms" hostId=<redacted>
app_server_connection.transport_connect_failed errorMessage="SSH: codex --version check timed out after 30000ms" hostId=<redacted>
connection_state_changed error={"code":"connection-failed","message":"SSH: codex --version check timed out after 30000ms"}

Expected behavior

If the app can complete the SSH path probe and manual ssh <alias> "codex --version" returns immediately, the Codex App version probe should also complete and proceed to app-server startup.

Actual behavior

Codex App Remote SSH fails the connection after 30 seconds at the installed Codex version probe, even though manual SSH version checks and codex app-server --help work.

Notes

This looks distinct from public-key/PAM authentication failures because manual public-key SSH succeeds, the app reaches the path probe, and codex_path_probe exits with code 0 before the timeout.

Related but not exact matches I found while searching: #20128, #23037.

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…

FAQ

Expected behavior

If the app can complete the SSH path probe and manual ssh <alias> "codex --version" returns immediately, the Codex App version probe should also complete and proceed to app-server startup.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING