Sign In with ChatGPT not working on browserless machines

Resolved 💬 4 comments Opened Aug 8, 2025 by mpelteshki Closed Aug 9, 2025
💡 Likely answer: A maintainer (edward-bayes, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.19.0

Which model were you using?

-

What platform is your computer?

Linux 6.8.0-1031-aws aarch64 aarch64

What steps can reproduce the bug?

  1. Run codex login on a browserless machine
  2. Says ‘if your browser did not open, navigate to x url
  3. I copy the link and open the url from my phone
  4. I go through the oauth process
  5. I get a failed redirect on my phone (tries to redirect to localhost:1455, that’s not on my phone at all but on my server)
  6. Codex cli is not authenticated

Will be happy to assist more :)

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

allquixotic · 1 year ago

Your web browser's address bar will have the localhost:1455 link; copy that and curl '<url>' that link on your headless box while codex login is waiting and it will work.

Mushus · 1 year ago

I'm having a similar issue. When I select "Sign in with ChatGPT" on the initial launch of Codex, my browser doesn't open. After I follow the "Press Enter to continue" prompt to cancel, a message appears with a URL: "Starting local login server on http://localhost:1455. If your browser did not open, navigate to this URL to authenticate:". However, the local callback server has already closed, so it doesn't work.

allquixotic · 1 year ago
I'm having a similar issue. When I select "Sign in with ChatGPT" on the initial launch of Codex, my browser doesn't open. After I follow the "Press Enter to continue" prompt to cancel, a message appears with a URL: "Starting local login server on http://localhost:1455. If your browser did not open, navigate to this URL to authenticate:". However, the local callback server has already closed, so it doesn't work.

It doesn't work with regular codex - you need codex login. That keeps the web server up.

edward-bayes contributor · 1 year ago