Closed AitBaali-Hamza-bcg closed 2 weeks ago
The issue FIXED. Redis was using in-transit encryption tls (NOTE: without any auth token), Redis extension can connect but couldn't communicate with Redis apparently, and this causes weird issues with Hocuspocus with no errors thrown, I am not sure how Redis extension can affect another part of Hocuspocus like this, but the issue is fixed by properly connecting to Redis by passing the Redis ioredis client to the Redis extension config.
Description The WebSocket connection to the Hocuspocus server drops and is ignored after the first reply from the server. The connection successfully opens, authentication and sync messages are exchanged, but the connection is subsequently closed without an error message. The issue seems to occur after the first document sync and awareness update.
Steps to reproduce the bug Steps to reproduce the behavior:
Expected behavior The WebSocket connection should remain open after the first reply from the server, allowing continuous synchronization of the document and awareness updates without being disconnected.
Screenshot, video, or GIF from browser:
From a script:
Script :
Environment?
Additional context hocuspocus works perfectly locally.