Skip to main content

Homeserver for the Matrix decentralised comms protocol

Project description

./docs/element_logo_white_bg.svg

Element Synapse - Matrix homeserver implementation

(get community support in #synapse:matrix.org) (discuss development on #synapse-dev:matrix.org) (Rendered documentation on GitHub Pages) (check license in LICENSE file) (latest version released on PyPi) (supported python versions)

Synapse is an open source Matrix homeserver implementation, written and maintained by Element. Matrix is the open standard for secure and interoperable real time communications. You can directly run and manage the source code in this repository, available under an AGPL license. There is no support provided from Element unless you have a subscription.

Subscription alternative

Alternatively, for those that need an enterprise-ready solution, Element Server Suite (ESS) is available as a subscription. ESS builds on Synapse to offer a complete Matrix-based backend including the full Admin Console product, giving admins the power to easily manage an organization-wide deployment. It includes advanced identity management, auditing, moderation and data retention options as well as Long Term Support and SLAs. ESS can be used to support any Matrix-based frontend client.

🛠️ Installing and configuration

The Synapse documentation describes how to install Synapse. We recommend using Docker images or Debian packages from Matrix.org.

Synapse has a variety of config options which can be used to customise its behaviour after installation. There are additional details on how to configure Synapse for federation here.

Using a reverse proxy with Synapse

It is recommended to put a reverse proxy such as nginx, Apache, Caddy, HAProxy or relayd in front of Synapse. One advantage of doing so is that it means that you can expose the default https port (443) to Matrix clients without needing to run Synapse with root privileges. For information on configuring one, see the reverse proxy docs.

Upgrading an existing Synapse

The instructions for upgrading Synapse are in the upgrade notes. Please check these instructions as upgrading may require extra steps for some versions of Synapse.

Platform dependencies

Synapse uses a number of platform dependencies such as Python and PostgreSQL, and aims to follow supported upstream versions. See the deprecation policy for more details.

Security note

Matrix serves raw, user-supplied data in some APIs – specifically the content repository endpoints.

Whilst we make a reasonable effort to mitigate against XSS attacks (for instance, by using CSP), a Matrix homeserver should not be hosted on a domain hosting other web applications. This especially applies to sharing the domain with Matrix web clients and other sensitive applications like webmail. See https://developer.github.com/changes/2014-04-25-user-content-security for more information.

Ideally, the homeserver should not simply be on a different subdomain, but on a completely different registered domain (also known as top-level site or eTLD+1). This is because some attacks are still possible as long as the two applications share the same registered domain.

To illustrate this with an example, if your Element Web or other sensitive web application is hosted on A.example1.com, you should ideally host Synapse on example2.com. Some amount of protection is offered by hosting on B.example1.com instead, so this is also acceptable in some scenarios. However, you should not host your Synapse on A.example1.com.

Note that all of the above refers exclusively to the domain used in Synapse’s public_baseurl setting. In particular, it has no bearing on the domain mentioned in MXIDs hosted on that server.

Following this advice ensures that even if an XSS is found in Synapse, the impact to other applications will be minimal.

🧪 Testing a new installation

The easiest way to try out your new Synapse installation is by connecting to it from a web client.

Unless you are running a test instance of Synapse on your local machine, in general, you will need to enable TLS support before you can successfully connect from a client: see TLS certificates.

An easy way to get started is to login or register via Element at https://app.element.io/#/login or https://app.element.io/#/register respectively. You will need to change the server you are logging into from matrix.org and instead specify a Homeserver URL of https://<server_name>:8448 (or just https://<server_name> if you are using a reverse proxy). If you prefer to use another client, refer to our client breakdown.

If all goes well you should at least be able to log in, create a room, and start sending messages.

Registering a new user from a client

By default, registration of new users via Matrix clients is disabled. To enable it:

  1. In the registration config section set enable_registration: true in homeserver.yaml.

  2. Then either:

    1. set up a CAPTCHA, or

    2. set enable_registration_without_verification: true in homeserver.yaml.

We strongly recommend using a CAPTCHA, particularly if your homeserver is exposed to the public internet. Without it, anyone can freely register accounts on your homeserver. This can be exploited by attackers to create spambots targeting the rest of the Matrix federation.

Your new user name will be formed partly from the server_name, and partly from a localpart you specify when you create the account. Your name will take the form of:

@localpart:my.domain.name

(pronounced “at localpart on my dot domain dot name”).

As when logging in, you will need to specify a “Custom server”. Specify your desired localpart in the ‘User name’ box.

🎯 Troubleshooting and support

🚀 Professional support

Enterprise quality support for Synapse including SLAs is available as part of an Element Server Suite (ESS) subscription.

If you are an existing ESS subscriber then you can raise a support request and access the knowledge base.

🤝 Community support

The Admin FAQ includes tips on dealing with some common problems. For more details, see Synapse’s wider documentation.

For additional support installing or managing Synapse, please ask in the community support room #synapse:matrix.org (from a matrix.org account if necessary). We do not use GitHub issues for support requests, only for bug reports and feature requests.

🪪 Identity Servers

Identity servers have the job of mapping email addresses and other 3rd Party IDs (3PIDs) to Matrix user IDs, as well as verifying the ownership of 3PIDs before creating that mapping.

They are not where accounts or credentials are stored - these live on home servers. Identity Servers are just for mapping 3rd party IDs to matrix IDs.

This process is very security-sensitive, as there is obvious risk of spam if it is too easy to sign up for Matrix accounts or harvest 3PID data. In the longer term, we hope to create a decentralised system to manage it (matrix-doc #712), but in the meantime, the role of managing trusted identity in the Matrix ecosystem is farmed out to a cluster of known trusted ecosystem partners, who run ‘Matrix Identity Servers’ such as Sydent, whose role is purely to authenticate and track 3PID logins and publish end-user public keys.

You can host your own copy of Sydent, but this will prevent you reaching other users in the Matrix ecosystem via their email address, and prevent them finding you. We therefore recommend that you use one of the centralised identity servers at https://matrix.org or https://vector.im for now.

To reiterate: the Identity server will only be used if you choose to associate an email address with your account, or send an invite to another user via their email address.

🛠️ Development

We welcome contributions to Synapse from the community! The best place to get started is our guide for contributors. This is part of our larger documentation, which includes

information for Synapse developers as well as Synapse administrators. Developers might be particularly interested in:

Alongside all that, join our developer community on Matrix: #synapse-dev:matrix.org, featuring real humans!

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

matrix_synapse-1.119.0rc2.tar.gz (3.7 MB view details)

Uploaded Source

Built Distributions

matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl (4.2 MB view details)

Uploaded PyPy manylinux: glibc 2.17+ i686 manylinux: glibc 2.5+ i686

matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-macosx_12_0_x86_64.whl (4.0 MB view details)

Uploaded PyPy macOS 12.0+ x86-64

matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl (4.2 MB view details)

Uploaded PyPy manylinux: glibc 2.17+ i686 manylinux: glibc 2.5+ i686

matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-macosx_12_0_x86_64.whl (4.0 MB view details)

Uploaded PyPy macOS 12.0+ x86-64

matrix_synapse-1.119.0rc2-cp39-abi3-musllinux_1_2_x86_64.whl (4.2 MB view details)

Uploaded CPython 3.9+ musllinux: musl 1.2+ x86-64

matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.2 MB view details)

Uploaded CPython 3.9+ manylinux: glibc 2.17+ x86-64

matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl (4.2 MB view details)

Uploaded CPython 3.9+ manylinux: glibc 2.17+ i686 manylinux: glibc 2.5+ i686

matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (4.1 MB view details)

Uploaded CPython 3.9+ manylinux: glibc 2.17+ ARM64

matrix_synapse-1.119.0rc2-cp39-abi3-macosx_12_0_x86_64.whl (4.0 MB view details)

Uploaded CPython 3.9+ macOS 12.0+ x86-64

File details

Details for the file matrix_synapse-1.119.0rc2.tar.gz.

File metadata

  • Download URL: matrix_synapse-1.119.0rc2.tar.gz
  • Upload date:
  • Size: 3.7 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.10.12

File hashes

Hashes for matrix_synapse-1.119.0rc2.tar.gz
Algorithm Hash digest
SHA256 5af3d986f5f7f99ad8b7dbdebd7b02c0d1eafe3aaadae325c0aa3474982c6bfa
MD5 197cf79f40bc61508368874bf857c5cb
BLAKE2b-256 9ec3e42dbf10cadfba00fc6434d822206fa3d2d585b5bde3c480f18566272197

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 d55819b71b64fc1a8e68d49cb5ca41cbd5b182cb5b3b1b02bc4341fe6d65660b
MD5 9a5ebf151e96ebcb53afdb39b00ac295
BLAKE2b-256 e3efd7d041b8e13cfbc81cb17b4f6bff016c554ef1dde18a769d0d44071b9cef

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl
Algorithm Hash digest
SHA256 5e8ac6439953e1995abf8047292e4934316294e9521c9fc3c937318d09797654
MD5 b39a3c4c974006a1fe0e2ce2877efaa2
BLAKE2b-256 6e96acef4bdad167092fc512b6fffa88a24da743679dec53dd05e4aae84abf8d

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-macosx_12_0_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp310-pypy310_pp73-macosx_12_0_x86_64.whl
Algorithm Hash digest
SHA256 200c02102430951a6ed958a9997e885c7bedf54b859d4283a7f9c81dd67a603a
MD5 65b8d831d45cd0179e31a7390a8a782b
BLAKE2b-256 04bc6ab28c3adf1914f3a503c1ab25383a0cab12f9219d94d86d3b1415f2cb73

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 fbc16fcc753055031c6d2318394464869467a084cf5275f0feb9a7e60a542195
MD5 892fcde00353d7ab80cef807f694069e
BLAKE2b-256 b90bf533f73bfae04230a93bcbb0bf1e3cf488fd860876545209d50382e1334d

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl
Algorithm Hash digest
SHA256 2a5d6fbc1bffb89eadbaeab3dd549e461bfa196243041357f9b0e795838a6655
MD5 8437796f4d8733199318b2dd6a08aa5c
BLAKE2b-256 21a48a196ac17608cb6fb46e777ab508b69a68135fb50af0355dfc212d462083

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-macosx_12_0_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-pp39-pypy39_pp73-macosx_12_0_x86_64.whl
Algorithm Hash digest
SHA256 a67a431969e4cd73124e9170efb5e3e735101c0cffa7ad0f4b0120b18f8996ce
MD5 47e6cfa7d1fee09630f27e8d749e3063
BLAKE2b-256 e22388ead122c4e3e17180eb24cc00b0fee2cf7652295d3e7fc2030a34eeab3a

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-cp39-abi3-musllinux_1_2_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-cp39-abi3-musllinux_1_2_x86_64.whl
Algorithm Hash digest
SHA256 b2d2c25d11b82ad12c164223b6dfeadf2d636a5baa3d77675115c74ddefcbb6b
MD5 c8ceb014bb3aadf4d652fa94398de747
BLAKE2b-256 4a291c85c5398d2b95cd7ff1c33fe9f5459f5e01a2e6a41a09d53db7699dc1e9

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 c2abf628df321becf98dc8a0f94b3c4d9b66c8307f6b385820a12f908b792747
MD5 f4687669b7b953e1aea05fd6ca2c46c6
BLAKE2b-256 a119cca1c9b6b40d1cddb3a2f1ded1e048c61ea62b0631213f20756527a2c5b4

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_i686.manylinux_2_5_i686.manylinux1_i686.manylinux2014_i686.whl
Algorithm Hash digest
SHA256 15b099c257b2f08e9bf223f50e6bb4883f255246d3c5a7ab228ca7c625ab57e5
MD5 c150dffe1e575df36d5b43f7f51f809a
BLAKE2b-256 777f5016049412b3b8a4dadc4419538bd414577fac535fb6e2e6a071aa3a60e0

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 ef3b8fd0960a3fd0a0c04d5bbd5d7ea0b0f36bddb473ccc0ce476457c5a63bd6
MD5 79c4d21cd717f6cb3c1cfda2d6eaebf9
BLAKE2b-256 4fe41ccae61010e51829505866e4a6d69474ec829815ffb40202c8186b88a9b4

See more details on using hashes here.

File details

Details for the file matrix_synapse-1.119.0rc2-cp39-abi3-macosx_12_0_x86_64.whl.

File metadata

File hashes

Hashes for matrix_synapse-1.119.0rc2-cp39-abi3-macosx_12_0_x86_64.whl
Algorithm Hash digest
SHA256 140df051e35d270a5171304b8ef748e109d00110f5d3fe544427d68699b8b672
MD5 9531f46c47775c777ad26aad2c9c4a63
BLAKE2b-256 481531972a146e94acba57d362de0b9672c7731e7c1ce918319855f65e2ab1ee

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page