WHAT IS THE BUG Self-hosted sync completely breaks after updating the Windows desktop client to v0.56.0. The client fails to connect to the self-hosted node and throws an EOF handshake error (gRPC connection drop). The issue is entirely client-side, as downgrading back to v0.55.x instantly resolves the issue with zero changes to the server infrastructure.
HOW TO REPRODUCE IT
-
Run a self-hosted Anytype network via Docker (updated to the latest node versions).
-
Route the traffic through a reverse proxy (in my case, Nginx Proxy Manager on a VPS).
-
Update the Windows desktop client to v0.56.0.
-
Attempt to log in or sync using the self-hosted network
.ymlconfig file. -
See the sync fail completely due to an
EOFhandshake error.
THE EXPECTED BEHAVIOR The client should successfully connect, authenticate, and sync with the self-hosted node through the reverse proxy, exactly as it seamlessly does in version 0.55.x.
ADDITIONAL CONTEXT
-
The definitive proof: Completely uninstalling v0.56.0, clearing the
%APPDATA%\Anytypecache, and installing v0.55.x restores full functionality immediately using the exact same.ymlfile. -
My setup consists of Docker nodes running on Unraid, tunneled through a Hetzner VPS running Nginx Proxy Manager.
-
The issue seems to be a regression in v0.56.0 regarding how the client handles mTLS certificates or gRPC streams when connecting through a standard reverse proxy.
-
Node logs during v0.56.0 connection attempts via local IP bypass showed absolutely zero incoming connection attempts reaching the
any-sync-node-1container, further pointing to a network routing/handshake issue introduced in the new client version.
TECHNICAL INFORMATION
-
OS: Windows 10/11
-
Client Version (Failing): v0.56.0
-
Client Version (Working): v0.55.x
-
Server Setup: Docker on Unraid + Nginx Proxy Manager