Skip to content

Repeated reconnects with Proxy URL scheme not supported while sending a simple prompt (stream disconnected before completion: URL error: Proxy URL scheme not supported) #14158

Closed as not planned

Description

@Danny-Tester

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?

Image

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.

Activity

  1. added
    appIssues related to the Codex desktop app
    on Mar 10, 2026
  2. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    on Mar 10, 2026
  3. github-actions commented on Mar 10, 2026

    @github-actions
    Contributor
  4. etraut-openai commented on Mar 10, 2026

    @etraut-openai
    Contributor

    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.

  5. Manouchehri commented on Mar 11, 2026

    @Manouchehri

    I had this error on Linux when using HTTPS_PROXY="https://example.com:8080" and HTTP_PROXY="https://example.com:8080".

    To fix it, I had to drop down to http://.

    export HTTPS_PROXY="http://example.com:8080"
    export HTTP_PROXY="http://example.com:8080"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions