فارسی · Components · Home
Core services
How to add any of these: Components.
Coturn TURN server
Relays voice and video calls between people whose networks don't let them connect directly (most phones on mobile data). Ticked by default; keep it.
Settings: Public IP address(es): your server's public IP. Empty means auto-detect, which needs the server to reach the internet.
Ports: open 3478 and 5349 (TCP and UDP) and 49152-49172/udp in any
firewall in front of the server. Review's z lists them.
After deploy: nothing to do. Calls in Element use it by themselves. Playbook doc
Exim email relay
Lets the server send email: password resets, sign-up verification codes from MAS, notifications of missed messages.
Settings:
- Sender address: the From address. Empty means
matrix@matrix.example.org. - Relay through another SMTP server: tick this unless you know your server can send mail by itself. Most VPS providers block port 25, and mail sent straight from a fresh server lands in spam. Then fill in your mail provider's SMTP host, port (usually 587) and, if it asks for them, username and password.
After deploy: use Forgot password in Element to send yourself a test. Playbook doc
Serve the base domain
For when nothing else runs on example.org: the server answers there too,
with a simple page and the /.well-known/matrix/… files other servers and
apps look for. Without them (or a website of yours serving them), federation
and app logins with example.org don't work.
DNS: an A record for example.org itself, pointing at the server.
After deploy: https://example.org/.well-known/matrix/server shows
{"m.server": "matrix.example.org:443"}.
Playbook doc
Dynamic DNS (ddclient)
For a server at home whose IP changes: keeps your DNS records pointing at it.
Settings: Provider configuration: replace the example with your DNS
provider's details. provider is its update server, protocol what it speaks
(Cloudflare, Namecheap, DuckDNS and many more are supported; see
ddclient's docs), and domain is the
record to keep updated. Add one block per record (matrix.example.org,
element.example.org…).
After deploy: nothing; it checks the IP every few minutes. Playbook doc
Use external PostgreSQL
Keeps Synapse's database on a Postgres server you run yourself instead of the one interzone installs. Only for people who already run Postgres.
Settings: the database's host, user, password and name. The database and its user must already exist.
Good to know: interzone's own database tools (backups, restore, vacuum, the Postgres upgrade, the database shell) work only on the bundled database, so Manage greys them out; back yours up where it runs. Playbook doc
Report anonymous usage stats
Synapse only. Sends matrix.org a few numbers about your server now and then: its domain, how many users and rooms, how many messages. Helps the Matrix developers; off by default. It needs the server to reach the internet. Playbook doc