Codex iphone&macbook connection failed. says Couldn’t update remote control availability

Open 💬 2 comments Opened Jul 9, 2026 by zx7ch
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.707.31123

What subscription do you have?

plus plan

What platform is your computer?

Darwin 21.6.0 arm64 arm

What issue are you seeing?

<img width="574" height="848" alt="Image" src="https://github.com/user-attachments/assets/5a669fc6-e967-48de-9ebf-67397d73b6b6" />

When I tried to add my iphone as connection on Codex App, there's no QR code shown up.
"Pairing code unavailable: Timed out waiting for remote control to connect"
I've tried refresh the connection and log out then log in on both devices, none of them works.

What steps can reproduce the bug?

Settings > Connections > Control this Mac > Allow Connections > add > no QR code shows up

What is the expected behavior?

Able to see the connection QR code

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #31161
  • #31231

Powered by Codex Action

boundless-forest · 9 days ago

I ran into the same issue and finally got it working. The underlying problem was that the Codex background process could not reliably connect to the Remote Control service through my network proxy. I used Proxifier to route Codex traffic through the proxy and enabled hostname resolution through the proxy instead of using local DNS.

I also changed the concrete GitHub entry in my SSH config from “Host github.com” to “Host github.*”, which prevented Codex from treating GitHub as a remote development host while preserving normal GitHub SSH access. After fully restarting the network proxy, Proxifier, and ChatGPT, the pairing code appeared and Remote Control connected successfully. Hope this helps anyone seeing the same timeout or TLS handshake error!