oAuth redirects me to localhost:1455/auth/callback?code=*** and token not set in CLI

Open 💬 9 comments Opened Dec 16, 2025 by alih70442
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.73.0

What subscription do you have?

busyness

Which model were you using?

gpt 5.2

What platform is your computer?

windows 11 x64

What issue are you seeing?

I Sign in with ChatGPT, after completing oAuth steps, finally it redirects me to http://localhost:1455/auth/callback?code= , and the setting codex cli token fails.

What steps can reproduce the bug?

just simple auth using Sign in with ChatGPT.

What is the expected behavior?

After oAuth the token should be set in my cli.

Additional information

_No response_

View original on GitHub ↗

9 Comments

alih70442 · 7 months ago

I found out that after selecting Sign in with ChatGPT , it generate a link that has redirect_to query param pointing to http://localhost:1455.
I use wsl on windows to use Codex CLI.

etraut-openai contributor · 7 months ago

Thanks for the bug report. This may be the same problem described in https://github.com/openai/codex/issues/4562 or https://github.com/openai/codex/issues/3927.

TriggerMoke · 7 months ago

Having this issue as well. Installed codex-cli 0.73.0 on Ubuntu server. Normal subscription

aaschenbach · 7 months ago

Same issue here. Ubuntu server. Normal subscription.

alih70442 · 7 months ago

Is there any temporary fix for this? For example, changing the host from http://localhost:1455/ to something that works. I am not sure if it is going to work by changing this. Any suggestions?

etraut-openai contributor · 7 months ago

As a workaround, you could try using the recently-introduced device code authentication mechanism. It was created for headless servers, dev containers, and remote shells, but it should work in this case too.

alih70442 · 7 months ago
As a workaround, you could try using the recently-introduced device code authentication mechanism. It was created for headless servers, dev containers, and remote shells, but it should work in this case too.

Thank you for your reply. I know this is working, but for some reason I couldn't use it. So finally I make it using this approach.

LXXXXSTAR · 4 months ago

@lizhian01大哥你是怎么解决你的问题的?

lizhian01 · 4 months ago
@lizhian01大哥你是怎么解决你的问题的?

https://github.com/openclaw/openclaw/issues/45036
代理开全局