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 | ||
|
digital:server:matrixsynapse [2021/01/28 15:17] natrius [Presence] added github issue for more information |
digital:server:matrixsynapse [2022/01/14 00:15] (current) natrius riot -> element; minor rewrite of Step 9 |
||
|---|---|---|---|
| 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 '8008' and '8448'. Check the open ports using ss (former netstat) command. | + | Synapse is now up and running using the default configuration on port ' |
| ss -plntu | ss -plntu | ||
| Line 218: | Line 218: | ||
| } | } | ||
| </ | </ | ||
| - | |||
| - | FIXME '' | ||
| - | |||
| - | FIXME Same for '' | ||
| Save and exit. | Save and exit. | ||
| Line 306: | Line 302: | ||
| ### Step 7 - Setup UFW Firewall | ### Step 7 - Setup UFW Firewall | ||
| - | Open the needed ports for our services. We will only allow SSH, HTTP, HTTPS and 8448 (for federation) | + | Open the needed ports for our services. We will only allow SSH, HTTP, and HTTPS connection on the UFW firewall configuration. To add them to the UFW firewall configuration, |
| sudo ufw allow ssh | sudo ufw allow ssh | ||
| sudo ufw allow http | sudo ufw allow http | ||
| sudo ufw allow https | sudo ufw allow https | ||
| - | sudo ufw allow 8448 | ||
| Now enable the UFW firewall service and then check the status. | Now enable the UFW firewall service and then check the status. | ||
| Line 328: | Line 323: | ||
| ### Step 9 - Testing | ### Step 9 - 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://riot.im/app/]] and press " | + | If you have used Element |
| - | The Synapse homeserver is up and running under the Nginx reverse proxy HTTPS connection, and the user is now logged in to the Synapse homeserver using the Riot application. | + | The Synapse homeserver is up and running under the Nginx reverse proxy HTTPS connection, and the user is now logged in to the Synapse homeserver using the Element |
| - | If you need two instances of riot instead, you can start it with argument, refer to [[digital: | + | If you need two instances of Element |
| For another way to test it, go to '' | For another way to test it, go to '' | ||
| Line 366: | Line 361: | ||
| ### Do i need a TURN-Server (ex. COTURN) | ### Do i need a TURN-Server (ex. COTURN) | ||
| - | It's only necessary when both parties are behind NAT. Otherwise 1-on-1 communication should work fine. Group-Calls via Riot will be handled with jitsi.riot.im and are not handled by the homeserver. | + | It's only necessary when both parties are behind NAT. Otherwise 1-on-1 communication should work fine. Group-Calls via Element |
| ### Port 8008 and 8448 | ### Port 8008 and 8448 | ||
| Line 412: | Line 407: | ||
| If your need help, get as much information as possible ([[# | If your need help, get as much information as possible ([[# | ||
| + | |||
| + | ### Problems with sending pictures | ||
| + | |||
| + | Open the '' | ||
| + | |||
| + | |||
| + | < | ||
| + | http{ | ||
| + | ... | ||
| + | | ||
| + | ... | ||
| + | } | ||
| + | </ | ||
| + | |||
| ### Whats my version | ### Whats my version | ||