Repeated reconnects with Proxy URL scheme not supported while sending a simple prompt (stream disconnected before completion: URL error: Proxy URL scheme not supported)
What version of the Codex App are you using (From “About Codex” dialog)?
Init
What subscription do you have?
Enterprise
What platform is your computer?
Windows 11 (x64)
What issue are you seeing?
<img width="1258" height="745" alt="Image" src="https://github.com/user-attachments/assets/89ac956d-9911-4a3d-866c-bc188b0a088a" />
When I send a simple prompt (for example, 123123123123123), Codex repeatedly tries to reconnect and then fails.
I see the following messages in sequence:
Reconnecting... 2/5
stream disconnected before completion: URL error: Proxy URL scheme not supported
Reconnecting... 3/5
stream disconnected before completion: URL error: Proxy URL scheme not supported
Reconnecting... 4/5
stream disconnected before completion: URL error: Proxy URL scheme not supported
Reconnecting... 5/5
stream disconnected before completion: URL error: Proxy URL scheme not supported
This happens even with very short/non-complex prompts.
What steps can reproduce the bug?
What steps can reproduce the bug?
Open Codex desktop app on Windows 11.
Start a new thread/session.
Enter a simple prompt such as 123123123123123.
Send the prompt.
Observe repeated reconnect attempts and final failure with Proxy URL scheme not supported.
I can reproduce this consistently.
What is the expected behavior?
The prompt should be processed normally without repeated reconnect attempts, and the response stream should complete successfully.
Additional information
The behavior suggests a proxy configuration/parsing issue.
It may be related to system or environment proxy settings (scheme format unsupported by the app/runtime).
If helpful, I can provide sanitized proxy-related environment variable values and more logs.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This means your proxy is not configured correctly or is not responding correctly to requests. You'll need to fix your configuration and/or your proxy. Let me know if you have questions
I'm going to close the issue because this isn't a Codex bug.
I had this error on Linux when using
HTTPS_PROXY="https://example.com:8080"andHTTP_PROXY="https://example.com:8080".To fix it, I had to drop down to
http://.