Previous Page

root@Datura - 2024-01-14

Matrix Chat Setup

In this tutorial we're going to setup a private matrix chat server along with VoIP support for the element desktop client.

Disclaimer: If you want this service to remain anonymous, make sure you at least keep TOR between you and the service from the VPS acquisition to actual service usage.

Initial Setup

First install the required packages:


apt install docker.io docker-compose
	

Then create the directories required:


mkdir /srv/matrix/data -p
chown -R 755 /srv/matrix/data
cd /srv/matrix

Then we'll create the docker-compose.yml file and the generateconfig.sh script:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat docker-compose.yml
version: "3.3"

services:
 synapse:
  image: "matrixdotorg/synapse:latest"
  container_name: "matrix_synapse"
  ports:
   - 8008:8008
  volumes:
   - "./data:/data" #it will look at the current directory where you save the file and look for the data folder inside
  environment:
   VIRTUAL_HOST: "m.datura.network"
   VIRTUAL_PORT: 8008
   LETSENCRYPT_HOST: "m.datura.network"
   SYNAPSE_SERVER_NAME: "m.datura.network"
   SYNAPSE_REPORT_STATS: "yes"
 coturn:
  image: instrumentisto/coturn:latest
  restart: unless-stopped
  volumes:
   - ./coturn/turnserver.conf:/etc/coturn/turnserver.conf
  ports:
   - 47160-47200:47160-47200/udp
   - 3478:3478
   - 5349:5349
  networks:
   - mybridge
networks:
 mybridge:
  driver: bridge

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat generateconfig.sh
#!/bin/bash

docker-compose run --rm -e SYNAPSE_SERVER_NAME=m.datura.network -e SYNAPSE_REPORT_STATS=yes synapse generate
	

My matrix server will have the "m.datura.network" domain name. The coturn config mentionned here is used for the VOIP support. Now let's generate the initial keys of the matrix server like so:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ ./generateconfig.sh
Creating network "matrix_default" with the default driver
Creating network "matrix_mybridge" with driver "bridge"
Setting ownership on /data to 991:991
Creating log config /data/m.datura.network.log.config
Generating config file /data/homeserver.yaml
Generating signing key file /data/m.datura.network.signing.key
A config file has been generated in '/data/homeserver.yaml' for server name 'm.datura.network'. Please review this file and customise it to your needs.

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ ls
coturn  data  docker-compose.yml  docker-compose.yml.coturn  generateconfig.sh  m.datura.network.conf.nginx

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ ls data -lash
total 20K
4.0K drwxr-xr-x 2  991  991 4.0K Jan 14 11:12 .
4.0K drwxr-xr-x 4 root root 4.0K Jan  4 13:50 ..
4.0K -rw-r--r-- 1 root root 1.3K Jan 14 11:12 homeserver.yaml
4.0K -rw-r--r-- 1 root root  694 Jan 14 11:12 m.datura.network.log.config
4.0K -rw-r--r-- 1 root root   59 Jan 14 11:12 m.datura.network.signing.key
	

Now that's done, we can edit the homeserver.yaml if you want to remove trust into the "matrix.org" keys for federation to make it a truly private server:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat data/homeserver.yaml | grep server

trusted_key_servers:
  - server_name: ""

Then we can edit the coturn config like so:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ ls
coturn  data  docker-compose.yml  docker-compose.yml.coturn  generateconfig.sh  m.datura.network.conf.nginx

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat coturn/turnserver.conf
use-auth-secret
static-auth-secret=cuAWWAAWWAAWWAWADDWADWADWADWADWADWAWADDWADWWADWADDWADWDWoy
realm=m.datura.network
listening-port=3478
tls-listening-port=5349
min-port=47160
max-port=47200
verbose
allow-loopback-peers
cli-password=cuAWWAAWWAAWWAWADDWADWADWADWADWADWAWADDWADWWADWADDWADWDWoy
external-ip=116.202.216.190	

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat data/homeserver.yaml | grep turn
turn_uris: [ "turn:m.datura.network?transport=udp", "turn:m.datura.network?transport=tcp" ]
turn_shared_secret: "cuAWWAAWWAAWWAWADDWADWADWADWADWADWAWADDWADWWADWADDWADWDWoy"
turn_user_lifetime: 86400000
turn_allow_guests: true


Make sure the ports match the ones in the docker-compose.yml file, and the external IP is the one of your server:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ curl ifconfig.me -4
116.202.216.190
	

Then we start the docker-compose:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ docker-compose up -d
Creating matrix_coturn_1 ... done
Creating matrix_synapse  ... done
	

Then we create the accounts like so:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ docker container ls | grep matrixdot
134d440b1480   matrixdotorg/synapse:latest                          "/start.py"              About a minute ago   Up 25 seconds (healthy)   8009/tcp, 0.0.0.0:8008->8008/tcp, :::8008->8008/tcp, 8448/tcp                                                                                                           matrix_synapse

[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ docker exec -it 134 bash
root@134d440b1480:/#
[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ docker exec -it 134 bash

root@134d440b1480:/# register_new_matrix_user -c /data/homeserver.yaml http://localhost:8008
New user localpart [root]: nihilist
Password:
Confirm password:
Make admin [no]: yes
Sending registration request...
Success!

root@134d440b1480:/# exit
exit

Then we make sure that we can access the matrix server via nginx:


[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ cat /etc/nginx/sites-enabled/m.datura.network.conf
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    # For the federation port
    listen 8448 ssl http2;
    listen [::]:8448 ssl http2;

    server_name m.datura.network;

        ssl_certificate                         /etc/acme/certs/m.datura.network/fullchain.cer;
        ssl_certificate_key                     /etc/acme/certs/m.datura.network/m.datura.network.key;

    location ~ ^(/_matrix|/_synapse/client) {
        # note: do not add a path (even a single /) after the port in `proxy_pass`,
        # otherwise nginx will canonicalise the URI and cause signature verification
        # errors.
        proxy_pass http://localhost:8008;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $host;

        # Nginx by default only allows file uploads up to 1M in size
        # Increase client_max_body_size to match max_upload_size defined in homeserver.yaml
        client_max_body_size 50M;

        # Synapse responses may be chunked, which is an HTTP/1.1 feature.
        proxy_http_version 1.1;
    }
}
	
[ Datura-Network ] [ /dev/pts/1 ] [/srv/matrix]
→ nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Then we test that we can login from a matrix client (which can be installed inside a whonix VM), let's use element because we want to be able to do voicecalls:

Here we will setup a secure backup password, that is a separate password, for end to end encryption purposes. Then you can do the following steps:

Make sure you log out of every unverified session:

You may need to log in and log out before being able to send messages so do that, then create the space along with the chatroom

Nihilism

Until there is Nothing left.

About nihilist

Donate XMR: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8


Contact: nihilist@nihilism.network (PGP)