You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"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
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.
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
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
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.
Activity
[-]"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[/+][-]"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[/+]bsergean commentedon Nov 17, 2026
The misleading
Connect error: No errorpath is fixed by merged PR #645. Writable/error readiness now checks the socket'sSO_ERRORon 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.