Set Up coturn for Reliable Matrix Voice and Video Calls
Configure coturn and Synapse with matching TURN credentials, open the required relay ports, and verify that Matrix clients can obtain relay candidates.
On the new Windows 10 operating system, managing users is now simple and it also gives you more options so you can control the user's Microsoft account. You can use more than one Microsoft account on a Windows 10 device.
It's fine if you're using a personal computer, but if you do use it, you will sometimes see another Microsoft account logged into your Windows 10 operating system. It is also no problem but you have to log out and log in to your account to use. If you want to manage the use of Microsoft account, you can follow the instructions in the article below.
Step 1: First click on Start , then scroll down and select Windows Administrator Tools , select Local Security Policy.

Step 2: In the Local Security Policy table, select Local Policies> Security Options , in the Policy pane on the right, double-click Account: Block Microsoft Accounts.
Step 3: In the Accounts selection box : Block Microsoft accounts Properties . You will have two options:
Details of these two options are below.
This is the Users can't add Microsoft accounts option in the Accounts table : Block Microsoft accounts Properties when you select this option, you will have the following features.
Corresponding to the option, Users can't add or log on with Microsoft accounts: This option will have the following features:
Based on the features available on the two options, you should choose the first option (Users can't add Microsoft accounts) to prevent users from adding Microsoft accounts to your Windows 10. Then click Apply and OK to finish.
Some computers have additional Microsoft account errors due to the above settings, so if you encounter errors, please check the settings in this custom.
Configure coturn and Synapse with matching TURN credentials, open the required relay ports, and verify that Matrix clients can obtain relay candidates.
Set up a persistent Synapse homeserver with Docker Compose, PostgreSQL, a private config, and checks before exposing it through HTTPS.
Set a branded name, custom colors, and login assets for your Element Web deployment while understanding which parts remain Element-branded.
Diagnose whether Synapse hit its per-process open-file cap, set a systemd drop-in for the right service or worker, and verify the live limit.
Find out whether the error is limited to one browser or one event, then use Element’s recovery key or a trusted device without risking your remaining encrypted history.
Use Synapse’s history and media purge APIs or retention settings to remove stale data safely, then verify completion and disk-space recovery.
Install the current library, connect a dedicated Matrix account, and run a small !echo bot with safer credential handling and a clear test.
Set up three mautrix bridges with separate registrations, logins, and tests—and avoid Docker networking, account-policy, and sync surprises.
Find what is filling Synapse storage, set safe media retention, and purge remote cache without deleting files directly from disk.
Review device activity, deactivate confirmed inactive Synapse accounts through the Admin API, and learn what the optional erase flag actually removes.