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
"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
Open
ProjectHSI opened this issue
Feb 21, 2025
· 0 comments
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.
The text was updated successfully, but these errors were encountered:
ProjectHSI
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
Feb 21, 2025
ProjectHSI
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
Feb 21, 2025
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.
The text was updated successfully, but these errors were encountered: