Alexander Rose

please check why your server responds to the http request with HTTP 501 (Internal**Server**Error) instead of running the GraphQL engine!

You can subscribe to `GraphQLHttpClient.WebsocketConnectionState` https://github.com/graphql-dotnet/graphql-client/blob/master/src/GraphQL.Client/GraphQLHttpClient.cs#L41

> Something on the server side I'd need to do? Maybe the server tells you why it doesn't like your request (status code 400). Which websocket subprotocol does your server...

Have you tried to subscribe to [`GraphQLHttpClient.WebSocketReceiveErrors`](https://github.com/graphql-dotnet/graphql-client/blob/10c22365ebce413ae3c4249518fecbfd415af575/src/GraphQL.Client/GraphQLHttpClient.cs#L42)? Maybe the problem surfaces there...

Inherit from `GraphQLHttpRequest` and override [ToHttpRequestMessage](https://github.com/graphql-dotnet/graphql-client/blob/dd418d16b690e503f054c5c355927cd91e8188d6/src/GraphQL.Client/GraphQLHttpRequest.cs#L37`), then use your new request class instead of the default one when creating requests.

I'm aware of an issue with the reconnect capability, seems there is a threading problem within the observable chain... Hopefully I'll be able to fix this in the coming days

The exception is as expected and you cannot call `closeAsync()` there because the websocket is in an aborted state. This is taken care of by `InitializeWebSocket()` which disposes the old...

Somehow this seems to be related with #161...

> that exception all the way pass to application Where does that exception surface? Does it call `OnError` on your subscription?

Did you pass a custom exception handler? This exception is normally swallowed by and causes a Retry on the subscription. Please also update to the latest version of this lib,...