Authentication Failed: Port Conflict Preventing Codex Authorization in VibeProxy

[dabaige53]

When authenticating Codex through VibeProxy, I encounter the following problem:
I log into Codex using my Google account, which is associated with a team. After selecting the project, the system displays "Authorization successful." However, no authorized account appears in VibeProxy.
When attempting to authenticate again, I receive the following error:
Authentication Result
Authentication failed. Please check if the browser opened and try again.

Details:
CLIProxyAPI Version: 6.6.53-0-plus, Commit: ed57d82, BuiltAt: 2025-12-24T15:31:59Z
[2025-12-26 09:19:49] ---] [info ] [main.go:442] CLIProxyAPI Version: 6.6.53-0-plus, Commit: ed57d82, BuiltAt: 2025-12-24T15:31:59Z
[2025-12-26 09:19:49][-- [error] [openai_login.go:55] The required port is already in use. Please close any applications using port 3000 and try again.
Environment:

VibeProxy Version: 6.6.53-0-plus
Commit: ed57d82
Built At: 2025-12-24T15:31:59Z

[pkral78]

Actually this is hardcoded error from CLIProxyAPIPlus, for Codex oauths server port listen at 1455, it got stuck somewhere during auth process and listening server needs to be killed then. Further reauth does not helps, we definitelly have to dig deeper in CLIProxyAPIPlus Codex auth code what is going on.

[ranaroussi]

This issue occurs when CLIProxyAPI's OAuth callback server on port 1455 gets stuck from a previous incomplete auth attempt.

Immediate fix:

# Kill any stuck process on port 1455
lsof -ti:1455 | xargs kill -9

# Then retry authentication in VibeProxy

Root cause: When the Codex login flow is interrupted (e.g., browser closed before completing, timeout, or network issue), the callback server on port 1455 may remain running.

Note: PR #123 addresses a related Codex login timeout issue. Once merged, it may help prevent some of these stuck scenarios.

@pkral78 is correct that this is internal to CLIProxyAPIPlus. We'll investigate if VibeProxy can better detect and clean up stuck OAuth processes.

[pkral78]

Actually for me, this PR #123 (which prolong timeouts) fix the cause.

[ranaroussi]

Friendly reminder: This issue will be closed in 7 days if we don't receive the requested information. Please provide the details above so we can help resolve your issue.