Bad message type 53 received from server. about clickhouse-net

[xontab]

Looks like this was caused during handshake. Which version of ClickHouse are you using? Can you use the default port 9000?

[killwort]

Either it is new clickhouse server version which I do not support (yet) or there's some protocol desync.
First of all try disabling compression - it is notorious for causing similar troubles due to slight differences in .net and c++ implementations.

[killwort]

Message code 53 is simply the type of message server sends in each packet header. It has no other special meaning. However for a long time clickhouse used these types <=8, so getting 53 here most probably means protocol desync.

[killwort]

I've reproduced this bug and it seems that it is not a bug at all :)
By default my driver uses TCP buffer of size 1024 - exactly the same that can be seen in CH's sources (at least in older versions) and despite that server sends bigger packets (in my case 1500+ bytes). This causes data loss upon receive and infinite waits upon consequent receives.

Bottom line:
To quickly fix without new binary version just set BufferSize=8192 (or whatever value you see reasonable) in your connection string.
Moreover, I'm changing default 1024 ripped from CH sources to 4096 as it definetaly has more sense.

[MagierCapo]

Although this issue has closed ...
I experience the same error "Bad message type 53 received from server" on connection.open();

My ConnString is "Host=localhost;Port=8123;User=default;Password=;BufferSize=8192;"
(I had to SSH-tunnel the Port 8123 to the remoteServer)

We are using .NET driver ClickHouse.Ado v1.1.17 and ClickHouse server version 19.7.3.1 revision 54419
You commented on 21 Jun 2018 "Either it is new clickhouse server version which I do not support (yet) or there's some protocol desync"

Is there an issue with this combination of CH-Versions ?

Or are there any other solutions?