Description
I recently enabled End-to-End Encryption (E2E) on my self-hosted Rocket.Chat server. However, I’m facing some issues:
When I create a new user (e.g., "Test"), upon logging in, Rocket.Chat does not prompt the user to set an E2E password, as I expected.
Additionally, when I log in with my admin account, the E2E password generated during the E2E activation does not work. I am unable to decrypt existing messages or access the encrypted content.
I followed the official guide and configuration seemed to go fine. No errors were thrown during setup.
Server Setup Information
Version of Rocket.Chat Server: [insert your version here]
Operating System: [Debian version, e.g., Debian 12]
Deployment Method: docker
Number of Running Instances: 1
DB Replicaset Oplog: Enabled
NodeJS Version: [insert version, e.g., 22.x.x]
MongoDB Version: [insert version, e.g., 7.0]
Proxy: nginx
Firewalls involved: No
Any additional Information
I deployed Rocket.Chat using Docker Compose with MongoDB configured as a single replica set.
I used the latest official Rocket.Chat image (registry.rocket.chat/rocketchat/rocket.chat:latest)
After enabling E2E, the "Setup Encryption Password" screen did not appear for new users.
The admin account shows encrypted messages but entering the previously saved encryption password has no effect.
No relevant errors in the logs so far.
I also tried restarting the server and creating a new user again, but no prompt appears.
Any ideas or suggestions to troubleshoot this would be appreciated!