Deployment Overview of Jitsi on Server¶
Prerequisites and Basic Requirements¶
To ensure a successful deployment, the following requirements must be met:
-
Operating System: Debian or Ubuntu.
-
Privileges: Root or sudo access is required for package installation and service management.
-
Domain Name: A valid Fully Qualified Domain Name (FQDN) pointing to the server IP.
-
Ports: The following ports must be open in the firewall:
-
80/tcp(HTTP) -
443/tcp(HTTPS) -
10000/udp(RTP/Video Stream)
FQDN of the final panel on the hostkey.in domain¶
The application uses a specific naming convention for its access URL based on the server ID.
| Parameter | Value | | Prefix | jitsi | | Domain | hostkey.in | | Full template | jitsi{Server_ID_from_Invapi}.hostkey.in |
File and Directory Structure¶
The deployment utilizes several directories for configuration, certificates, and proxy management:
-
/etc/nginx/sites-available/: Contains the Nginx virtual host configuration files. -
/etc/nginx/sites-enabled/: Contains symbolic links to active Nginx configurations. -
/data/nginx/user_conf.d/: Stores custom Nginx proxy configurations. -
/root/nginx/: Contains the Docker Compose deployment for SSL management. -
/usr/share/jitsi-meet/scripts/: Location of the Let's Encrypt installation script.
Application installation process¶
The application is installed using a combination of package management and configuration scripts:
-
Dependency Installation: The system installs base dependencies including
curl,gnupg,apt-transport-https, andca-certificates. -
Repository Setup:
-
The Jitsi official repository is added to the system.
-
The Prosody repository is added using a dedicated keyring located at
/usr/share/keyrings/prosody-debian-packages.key. -
Package Installation: The following core packages are installed via
apt: -
jitsi-meet -
jicofo -
jitsi-videobridge2 -
jitsi-meet-prosody -
jitsi-meet-web -
jitsi-meet-web-config -
jitsi-meet-turnserver -
nginx -
Configuration: The application is preconfigured with the server's FQDN and set to use Let's Encrypt for SSL certificate management.
-
SSL Provisioning: An installation script located at
/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.shis executed to obtain valid certificates.
Access Rights and Security¶
Security is managed through the Uncomplicated Firewall (UFW):
-
The firewall is installed and enabled with a default policy of
allow. -
Specific rules are applied to permit traffic on:
-
TCP port
80 -
TCP port
443 -
UDP port
10000
Databases¶
The application utilizes Prosody as the XMPP server/database component. It is installed via the jitsi-meet-prosody package and managed as a system service.
Docker Containers and Their Deployment¶
A Docker container is used specifically for managing SSL certificates through Nginx and Certbot:
Nginx-Certbot Container
-
Image:
jonasal/nginx-certbot:latest -
Network Mode:
host -
Environment Variables:
-
CERTBOT_EMAIL: The administrative email for certificate notifications. -
Volumes:
-
nginx_secrets:/etc/letsencrypt(Persistent storage for SSL certificates) -
/data/nginx/user_conf.d:/etc/nginx/user_conf.d(Mapping custom proxy configurations)
Custom Scripts and Additional Setup¶
The deployment performs several automated configuration steps:
-
Nginx Proxy Configuration: A custom Nginx configuration is generated in
/data/nginx/user_conf.d/to act as a reverse proxy. It handles: -
HTTP to HTTPS redirection (Port 80).
-
Reverse proxying for web traffic, WebSocket connections (
/xmpp-websocket,/colibri-ws/), and STUN/TURN signaling (/http-bind) to the internal Jitsi service running on port8443. -
Service Management: After configuration, the following services are automatically restarted to apply changes:
-
prosody -
jicofo -
jitsi-videobridge2 -
nginx
Application Update Instructions¶
To update the main Jitsi application components, use the standard package manager:
Location of configuration files and data¶
-
Nginx Configuration:
/etc/nginx/sites-available/{FQDN}.conf -
Jitsi Web Config: Managed via
jitsi-meet-web-config. -
SSL Certificates: Managed within the Docker volume
nginx_secrets.
Available ports for connection¶
| Port | Protocol | Purpose |
|---|---|---|
| 80 | TCP | HTTP (Redirect to HTTPS) |
| 443 | TCP | HTTPS (Web Interface & Signaling) |
| 10000 | UDP | Media Streams (Video/Audio) |
Starting and Stopping the application¶
The application components are managed via systemd.
-
Restarting all services:
-
Stopping a service (e.g., Videobridge):
Proxy Servers¶
The deployment uses Nginx as a reverse proxy to handle SSL termination and routing. It directs external traffic from port 443 to the internal Jitsi service listening on 127.0.0.1:8443. Certbot is utilized within a Docker container to automate the acquisition and renewal of Let's Encrypt certificates for the configured domain.