C
C#•3y ago
Strikeeaglechase

❔ Websocket connection fails, however a javascript websocket can connect to server fine

I am using System.Net.WebSockets to create a websocket client to a websocket server I am running. The following code is used to create the websocket 
Debug.Log("Setting up websocket");
client = new ClientWebSocket();
await client.ConnectAsync(new Uri("ws://192.168.68.93:8001/ws"), System.Threading.CancellationToken.None);
Debug.Log($"Socket status: {client.State}");
Debug.Log("Setting up websocket");
client = new ClientWebSocket();
await client.ConnectAsync(new Uri("ws://192.168.68.93:8001/ws"), System.Threading.CancellationToken.None);
Debug.Log($"Socket status: {client.State}");
The following error is produced: System.Net.WebSockets.WebSocketException (0x80004005): Unable to connect to the remote server ---> System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. The confusing part to me, the following code in javascript works perfectly fine 
const ws = new WebSocket("ws://192.168.68.93:8001/ws")
const ws = new WebSocket("ws://192.168.68.93:8001/ws")
And if I log the messages I receive, they are what I expect/work perfectly fine. What would cause a JS websocket to work, but not a C# one?
2 Replies
Strikeeaglechase
StrikeeaglechaseOP•3y ago
My current suspicion is the issue is actually related to the wsserver, I am running it on an esp32, using a library called ESPAsyncWebServer. But I need to know why C# would fail on it when JS works fine
Accord
Accord•2y ago
Looks like nothing has happened here. I will mark this as stale and this post will be archived until there is new activity.

Did you find this page helpful?