meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
digital:server:matrixsynapse [2019/06/30 18:30] natrius Step 6 - spelling errors |
digital:server:matrixsynapse [2020/06/17 19:33] natrius [Step 2 - Install Synapse] - spelling error in example url |
||
---|---|---|---|
Line 63: | Line 63: | ||
sudo systemctl enable matrix-synapse.service | sudo systemctl enable matrix-synapse.service | ||
- | Synapse is now up and running using the default configuration on port ' | + | Synapse is now up and running using the default configuration on port ' |
- | | + | ss -plntu |
- | #### Set up well.known | + | #### Set up .well-known |
On your webserver a file at '' | On your webserver a file at '' | ||
Line 77: | Line 77: | ||
</ | </ | ||
- | Where ''/'' | + | Where ''/'' |
- | + | ||
- | #### Set up SRV | + | |
- | + | ||
- | By setting an SRV record in your DNS provider, it is possible to tell other matrix servers where to connect to the server, pointing them to the correct hostname and port, in this example the default port (8448) is still used: | + | |
- | + | ||
- | < | + | |
- | _matrix._tcp.example.com. 3600 IN SRV 10 5 443 synapse.example.com. | + | |
- | </ | + | |
- | + | ||
- | There is still an A record needed, pointing to the IP-addess of synapse on the subdomain (matrix.example.com). This way others can add your user with '' | + | |
### Step 3 - Configure Synapse | ### Step 3 - Configure Synapse | ||
Line 131: | Line 121: | ||
Check the homeserver service with the following command | Check the homeserver service with the following command | ||
- | | + | ss -plntu |
You will get the Synapse service is now on the local IP address. And we have completed the Synapse installation and configuration. | You will get the Synapse service is now on the local IP address. And we have completed the Synapse installation and configuration. | ||
Line 301: | Line 291: | ||
* '' | * '' | ||
- | * '' | + | * '' |
* '' | * '' | ||
Line 312: | Line 302: | ||
### Migrating from SQlite to PostgreSQL | ### Migrating from SQlite to PostgreSQL | ||
- | There is no need for this if you have nothing done yet with synapse, otherwise, please refer to https:// | + | Assuming you already followed step 6, there is no need for a migration. If you already used your Synapse and want to migrate, please refer to https:// |
### Step 7 - Setup UFW Firewall | ### Step 7 - Setup UFW Firewall | ||
Line 336: | Line 326: | ||
Now you need to input the user name, password, and decide whether the user will have the admin privileges or not. And we have created a new matrix user with admin privilege. | Now you need to input the user name, password, and decide whether the user will have the admin privileges or not. And we have created a new matrix user with admin privilege. | ||
- | ### Step 9 - Federation | + | ### Step 9 - Testing |
- | + | ||
- | You can test if federation is working using https:// | + | |
- | + | ||
- | * https:// | + | |
- | + | ||
- | ### Step 10 - Testing | + | |
If you have used Riot with the desktop application before you may not want to log out, so it is better to go to [[https:// | If you have used Riot with the desktop application before you may not want to log out, so it is better to go to [[https:// | ||
Line 350: | Line 334: | ||
If you need two instances of riot instead, you can start it with argument, refer to [[digital: | If you need two instances of riot instead, you can start it with argument, refer to [[digital: | ||
- | For another way to test it, go to '' | + | For another way to test it, go to '' |
<code xml> | <code xml> | ||
Line 361: | Line 345: | ||
3 " | 3 " | ||
</ | </ | ||
+ | |||
+ | ### Step 10 - Federation | ||
+ | |||
+ | You can test if federation is working using https:// | ||
+ | |||
+ | * https:// | ||
## Explanations | ## Explanations |