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
Hi! When I try to connect with the client on my local server everything works fine, but when I use my cloud environment I have the following error:
TestSocket: Failed to connect to Unspecified/some.domain.com:443System.Net.Sockets.SocketException (11004): The requested name is valid, but no data of the requested type was found. at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken) at SuperSocket.Client.SocketConnector.ConnectAsync(EndPoint remoteEndPoint, ConnectState state, CancellationToken cancellationToken)
Library version
v1.0.0-beta.5
Reproduction Steps
usingWebSocket=WebSocket4Net.WebSocket;varws=newWebSocket("wss://some.domain.com/");ws.Headers.Add("Sec-WebSocket-Extensions","permessage-deflate; client_max_window_bits");//Throws the exception hereawaitws.OpenAsync(cancellationToken).ConfigureAwait(false);
Additional Information
If I use ws://localhost:8080 instead, the issue is not happening.
Looks like it may be related to a DNS lookup issue, but I am not sure why since the native websocket is able to connect without issue.
The text was updated successfully, but these errors were encountered:
The bug
Hi! When I try to connect with the client on my local server everything works fine, but when I use my cloud environment I have the following error:
Library version
v1.0.0-beta.5
Reproduction Steps
Additional Information
If I use
ws://localhost:8080
instead, the issue is not happening.Looks like it may be related to a DNS lookup issue, but I am not sure why since the native websocket is able to connect without issue.
The text was updated successfully, but these errors were encountered: