From d37ba35c3c7c1f54a642a1ab1eb6bcc41b6430af Mon Sep 17 00:00:00 2001 From: Arthur Wolf Date: Fri, 27 Mar 2026 16:54:40 +0100 Subject: [PATCH] Enable MLS protocol in production values Mohit had me deploy a wire-server (wire in a box) install following the current instructions. The install itself went mostly well, but recently I tried to set up a new user and log into the webapp, and that produced an error related to MLS/Proteus. The fix was to change the brig config `setEnableMLS` to `true`, which caused the backend and frontend to "match". This is a commit aimed at creating a PR that fixes this issue moving forward. --- values/wire-server/prod-values.example.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/values/wire-server/prod-values.example.yaml b/values/wire-server/prod-values.example.yaml index a0e8a2c67..31932fbe5 100644 --- a/values/wire-server/prod-values.example.yaml +++ b/values/wire-server/prod-values.example.yaml @@ -55,7 +55,7 @@ brig: teamMemberWelcome: https://wire.example.com/download # change this enableFederation: false # Keep false unless federation is explicitly configured optSettings: - setEnableMLS: false # Enable for MLS protocol use + setEnableMLS: true # Enable for MLS protocol use setFederationDomain: example.com # change this per host deployment # Sync the domain with the 'host' variable in the sftd chart # Comment the next line (by adding '#' before it) if conference calling is not used