The server didn't accept the connection request. It is possible that the client side message encoding format doesn't match the setting on the server side. Please check your binding settings.
The server cannot access the application directory {0}. This may be due to the presence of Unicode characters in the URL. ...
The server certificate with name '{0}' failed identity verification because its thumbprint ('{1}') does not match the one ...
The server challenged this request and streamed requests cannot be resubmitted. To enable HTTP server challenges, set your ...
The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown ...
The server didn't accept the connection request. It is possible that the client side message encoding format doesn't match ...
The server didn't accept the connection request. It is possible that the client side message encoding format or message transfer ...
The server didn't accept the connection request. It is possible that the WebSocket protocol version on your client doesn't ...
The server didn't accept the connection request. It is possible that the WebSocket subprotocol sent by your client is not ...
The server encountered an error processing the request. Please see the service help page for constructing valid requests ...