@
.matrix.example.com
, and a SRV record with the hostname _matrix._tcp
pointing to the same subdomain on port 8448
, with the default priority and weights of 10 and 100 respectively. This will tell Matrix clients and homeservers where to find your Synapse installation.systemctl
to automatically start Synapse whenever your server starts up.systemctl
manually to start Synapse now.nano
or your favorite text editor.registration_shared_secret
key. Update its value to the random string you copied, inserting it between quotation marks (' '
). Remember to activate the key by uncommenting the line (i.e. deleting the #
at the beginning of the line).enable_registration
to True
here.-c
flag specifies the configuration file, and uses the local Synapse instance which is listening on port 8448
.https://example.com/_matrix/
to connect to Synapse. You’ll need to configure Nginx to listen for these requests and pass them on to Synapse, which is listening locally on port 8008
. You’ll also secure your setup by using SSL backed by Let’s Encrypt.location /_matrix
block below specifies how Nginx should handle requests from Matrix clients. In addition to the request handling, the /.well-known
block makes the directory of the same name available to Let’s Encrypt./etc/nginx/sites-enabled
directory.systemctl
reload Nginx so the changes take effect./etc/nginx/sites-available/example.com
instead of the default configuration file. You’ve already added the ~/.well-known
block mentioned in Step 2 of that tutorial.443
, (which is already open in your firewall from the Nginx guide). However, traffic from other servers connects directly to Synapse on port 8448
without going through the Nginx proxy, so you need to allow this traffic through the firewall as well.nano
or your favorite text editor.@user:server_name
(e.g. @sammy:example.com
). Other federated servers use this to find where your homeserver is hosted.#matrix:matrix.org
.