Room creation fails with "Encryption is already enabled!" on servers that encrypt by default #29

New issue

Open

opened 2026-10-05 19:03:37 +00:00 by robocub · 0 comments

robocub commented

2026-10-05 19:03:37 +00:00

Owner

Upstream: commetchat/commet#864

On servers configured to encrypt new private rooms by default (e.g. encryption_enabled_by_default_for_room_type: invite), creating an encrypted room errors with Encryption is already enabled!: the client tries to enable encryption on a room that already has it. Fix: treat already-encrypted as success, or put m.room.encryption in initial_state and skip the follow-up call.

Imported from Commet's tracker during the 2026-10-05 triage. As of that date it was open upstream with no assignee and no open PR. Nothing gets posted back to their tracker. If upstream fixes it first, close this issue and drop our patch on the next rebase (record the change in VOMMET_CHANGES.md).

Upstream: [commetchat/commet#864](https://github.com/commetchat/commet/issues/864) On servers configured to encrypt new private rooms by default (e.g. `encryption_enabled_by_default_for_room_type: invite`), creating an encrypted room errors with *Encryption is already enabled!*: the client tries to enable encryption on a room that already has it. Fix: treat already-encrypted as success, or put `m.room.encryption` in `initial_state` and skip the follow-up call. --- *Imported from Commet's tracker during the 2026-10-05 triage. As of that date it was open upstream with no assignee and no open PR. Nothing gets posted back to their tracker. If upstream fixes it first, close this issue and drop our patch on the next rebase (record the change in VOMMET_CHANGES.md).*

robocub added the

bug

effort: small

upstream

labels

2026-10-05 19:03:37 +00:00