Back to articles
Security & Anti-DDoS

Guide to Configuring a VPS to Run a Decentralized PubSub Network Using Matrix Protocol for Super Secure Internal Chat

A detailed guide on configuring a VPS to run a super secure internal chat system using Matrix Protocol, combining modern security techniques like WireGuard, Opaque Routing, and Zero...

DPTCloud Engineering4 min read
Guide to Configuring a VPS to Run a Decentralized PubSub Network Using Matrix Protocol for Super Secure Internal Chat

Image credit: superdirk · Pixabay Content License

Introduction to Matrix Protocol and Super Secure Internal Chat

Matrix Protocol is an open, decentralized communication protocol that enables the creation of super secure internal chat systems, independent of centralized platforms like Facebook, Slack, or WhatsApp. With a decentralized pubsub (public-subscribe) architecture, Matrix allows each user or organization to operate their own server (homeserver), ensuring full control over data and privacy.

In this guide, you will learn how to configure a VPS (Virtual Private Server) to run a Matrix homeserver, integrating modern security techniques such as WireGuard, Opaque Routing, and Zero Trust, to create a super secure internal chat system suitable for enterprises or sensitive workgroups.

Requirements and Pre-Configuration

Before starting, ensure you have:

  • A VPS (Cloud VPS) from DPTCloud with Anti-DDoS Anycast L3/L4/L7 capabilities.
  • A static IP address and root or sudo access.
  • Required software: Docker, Nginx, WireGuard, and tools like matrix-synapse and matrix-appservice-irc.
  • DNS configured with A and CNAME records for your domain (e.g., matrix.yourdomain.com).

Configuring the Matrix Homeserver

Matrix homeservers can be deployed easily using Docker. Follow these steps to set up the basic configuration:

1. Install Docker and Matrix Synapse

Run the following commands on your VPS:

# Install Docker
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh

# Create configuration directory
mkdir -p /opt/matrix-synapse
cd /opt/matrix-synapse

# Create docker-compose.yml
cat > docker-compose.yml << EOF
version: '3.8'

services:
  synapse:
    image: matrixdotorg/synapse:latest
    container_name: matrix-synapse
    restart: unless-stopped
    volumes:
      - ./data:/data
      - ./config:/config
    ports:
      - "8008:8008"
      - "8448:8448"
    environment:
      - SYNAPSE_SERVER_NAME=yourdomain.com
      - SYNAPSE_REPORTING=false
      - SYNAPSE_POSTGRES_HOST=postgres
      - SYNAPSE_POSTGRES_PORT=5432
    networks:
      - matrix-network

  postgres:
    image: postgres:14
    container_name: matrix-postgres
    restart: unless-stopped
    volumes:
      - ./postgres_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=matrix
      - POSTGRES_USER=matrix
      - POSTGRES_PASSWORD=your_secure_password
    networks:
      - matrix-network

networks:
  matrix-network:
    driver: bridge
EOF

2. Configure Nginx as Reverse Proxy

To protect the Matrix homeserver from direct attacks, use Nginx as a reverse proxy and enable HTTPS:

# /etc/nginx/sites-available/matrix
server {
    listen 80;
    server_name matrix.yourdomain.com;
    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl;
    server_name matrix.yourdomain.com;

    ssl_certificate /etc/letsencrypt/live/matrix.yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/matrix.yourdomain.com/privkey.pem;

    location /_matrix {
        proxy_pass http://127.0.0.1:8008;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location /_synapse/client {
        proxy_pass http://127.0.0.1:8008;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Enhanced Security with WireGuard and Opaque Routing

To ensure the internal chat system remains undetectable and protected from attacks, integrate the Matrix homeserver with:

  • WireGuard: Establish an anonymous VPN tunnel between users and the VPS, encrypting all traffic.
  • Opaque Routing: Hide packet paths to prevent IP tracking.
  • V2Ray: Enhance firewall bypass capabilities and obscure traffic.

Refer to the article: Invisible Security: Turn Your VPS into an Anonymized Gateway with WireGuard, Opaque Routing, and V2Ray.

Authentication and Verification

After configuration, verify the system using the following commands:

# Check service status
docker-compose ps

# Test Matrix connection
curl -k https://matrix.yourdomain.com/_matrix/client/versions

# Check SSL certificate
openssl s_client -connect matrix.yourdomain.com:443 -servername matrix.yourdomain.com

Troubleshooting

  • Cannot access Matrix homeserver: Verify Nginx configuration, DNS records, and firewall rules.
  • Matrix fails to recognize users: Check Synapse configuration file and ensure SYNAPSE_SERVER_NAME is correct.
  • No WireGuard tunnel connection: Validate keys, IP addresses, and tunnel settings.

References

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478