Codex login redirects to an unreachable localhost:1455
Retry from the client, then check the local callback or device-code sign-in.
Start here
Start sign-in from the client again and keep it open. CLI users can try device-code sign-in when it is enabled.
On this page
1. Restart sign-in from the client
- Close the failed authorization page and start sign-in again. For CLI, run the command below in a regular terminal.
- Use the newly opened link and keep the client and terminal running throughout authorization.
codex login2. Check where each part is running
- For a local client, authorize in a browser on the same computer.
- For CLI in a remote server or container, try device-code sign-in in step 4. localhost refers to the browser’s computer.
3. Windows: inspect port 1455
- If the callback uses 1455, run the read-only command below in a separate PowerShell window while sign-in is waiting.
- With no output, restart sign-in. With output, identify the process and normally quit only a confirmed old Codex instance before retrying.
Get-NetTCPConnection -LocalPort 1455 -State Listen -ErrorAction SilentlyContinue | Select-Object LocalAddress,LocalPort,OwningProcess4. CLI: use device-code sign-in
- Enable device-code login in ChatGPT security settings; an administrator must allow it for organization accounts.
- Run the command below, open its displayed link and enter this attempt’s code. Then run codex login status and send a short test.
codex login --device-auth5. Contact support
- State whether you use desktop, IDE or CLI, whether it is remote and where sign-in stops.
- Hide the full callback URL and authorization code in screenshots so support can help check the issue.