Skip to content

"Unable to connect to localhost on port 1702, error: Connect error: No error" when trying to connect to localhost:1702 and other IP addresses NO MATTER WHAT #543

Closed

Description

@ProjectHSI

Exact URL: ws://localhost:1702/commands_editor

Of note: This specific port will work when connecting via the browser (about:blank, "new Websocket("ws://localhost:1702/[etc]"). The server is running and can be connected to (signified by the intended client running fine and the browser connecting and "working" just fine).

Of additional note: I can't change the server code, but the server doesn't seem to be related here, since the message shows up even if the server isn't running.

The server does not use TLS.

occurs in both the WS example application and in my own app.

Activity

  1. changed the title [-]"Unable to connect to localhost on port 1702, error: Connect error: No error" when trying to connect to a localhost IP NO MATTER WHAT[/-] [+]"Unable to connect to localhost on port 1702, error: Connect error: No error" when trying to connect to localhost:1702 NO MATTER WHAT[/+] on Feb 21, 2025
  2. changed the title [-]"Unable to connect to localhost on port 1702, error: Connect error: No error" when trying to connect to localhost:1702 NO MATTER WHAT[/-] [+]"Unable to connect to localhost on port 1702, error: Connect error: No error" when trying to connect to localhost:1702 and other IP addresses NO MATTER WHAT[/+] on Feb 21, 2025
  3. bsergean commented on Nov 17, 2026

    @bsergean
    Collaborator

    The misleading Connect error: No error path is fixed by merged PR #645. Writable/error readiness now checks the socket's SO_ERROR on Windows and POSIX, preserves the native error before closing the descriptor, and formats Winsock errors through the native system category. A missing native error now gets an explicit fallback diagnostic instead of “No error”.

    This applies to the plain ws:// URL in this report; it is independent of TLS certificate settings. Closing the incorrect-diagnostic report. If a running server still cannot be reached with current master, please reopen with the new error and a minimal client/server or endpoint reproduction—the diagnostic fix does not establish that every original server/network configuration will connect.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions