I am currently running a self-hosted CryptPad instance using Docker Compose, and I’m exploring the possibility of scaling the deployment horizontally by adding multiple nodes for improved availability and performance.
To test this, I’ve configured multiple CryptPad nodes with a shared storage backend using s3fs, mounting both the data and onlyoffice directories to a common S3 bucket. However, I’ve encountered issues with user synchronization—when a user registers on one node, logging in from another node results in an “invalid username or password” error. Unfortunately, I wasn’t able to find any official documentation on scaling CryptPad in a multi-node setup. Could anyone please clarify:
- Is there any official or community-supported documentation on horizontally scaling CryptPad?
- What is the recommended method for syncing user and document data between nodes in a multi-instance setup?
- Are shared storage solutions like S3 (via s3fs) supported for this use case, or are there known limitations?
- Is node-level load balancing possible for CryptPad in production, and if so, what are the best practices?
Any guidance would be greatly appreciated as I work toward building a scalable and robust CryptPad deployment.
