Technical requirements
This document describes the hardware requirements and other necessary steps for installation of SalaX Secure Messaging software.
1. Server Requirements
Recommended Minimum Server Requirements
| Users in Server | Open Federation Specs | Closed Federation Specs | Video Conference Specs |
|---|---|---|---|
| 0-99 | 5 vCpu, 6 GB Ram | 3 vCpu, 3 GB Ram | 3 vCpu, 5 GB Ram |
| 100-299 | 5 vCpu, 6 GB Ram | 3 vCpu, 3 GB Ram | 9 vCpu, 15 GB Ram |
| 300-499 | 8 vCpu, 8 GB Ram | 3 vCpu, 6 GB Ram | 16 vCpu, 32 GB Ram |
| 500-999 | 8 vCpu, 10 GB Ram | 5 vCpu, 10 GB Ram | 32 vCpu, 64 GB Ram |
| 1000-1999 | 10 vCpu, 16 GB Ram | 7 vCpu, 15 GB Ram | 64 vCpu, 128 GB Ram |
| 2000+ | decide based on users | decide based on users | decide based on users |
Standard Server Specifications for Customers Hosted by SSH
For Secure Messaging hosted by SSH, the server specifications are provided below. SSH retains the right to revise these specifications as deemed necessary and may apply additional charges for any supplementary server resources required.
| User Amount per Server | vCPU | RAM | Storage |
|---|---|---|---|
| 0 to 99 | 8 vCpu | 16 GB Ram | 100 GB |
| 100 to 299 | 16 vCpu | 32 GB Ram | 300 GB |
| 300 to 499 | 32 vCpu | 64 GB Ram | 500 GB |
| 500 to 999 | 64 vCpu | 192 GB Ram | 1000 GB |
| 1000 to 1999 | 80 vCpu | 512 GB Ram | 2000 GB |
| 2000+ | to be agreed separately |
2. Hardware Requirements
Desktop
- Windows, Linux, or macOS
- Both Arm and Intel processors are supported.
- The minimum recommended RAM is 4 GB.
Tablet
- Ipads with IpadOS 14 or later
- Android devices with Android 10 or later
Mobile
- iPhones with iOS 14 or later
- Android devices with Android 10 or later. TIP: Fast CPU improves the video call quality.
Browser
Android and Desktop
- Chrome: 72 or later
- Firefox: 68 or later
- Safari: 14 or later
- Edge: 79 or later
iOS and iPads
- Safari: 14.3 or later
3. Operating System
Rocky Linux 8 or 9 RHEL 8 or 9
4. Network connections and IP Addresses
4.1. Requirements
Servers are placed into the network so that a secure or reliable connection to mail servers can be made. Server requires one public IP address. This address acts as cluster address which e-mail traffic is relayed to. If NAT is used in address translation, information of both public and network address translated addresses is needed.
4.2. Options
• It is recommended that web-based management tool is separated from public network by defining D-Center with its own IP address and own port (default 443).
4.3. Firewall settings requirements
Firewall must allow the required connections. The following table shows requirements for basic installation; rules must be specified.
| Protocol | Port(s) | Usage |
|---|---|---|
| TCP | 1081 | Initial FQDN check, can be disabled post-installation |
| TCP | 80, 443 | Port 80 used for Letsencrypt, 443 for Http access |
| TCP | 3478, 5349 | Used by Turn server |
| UDP | 3478, 5349 | Used by Turn server |
| UDP | 40000-40500 | Used by turn server |
| UDP | 30300 | Used for the audio and video in conference |
4.4. DNS. Required FQDNs
SalaX Wellknown URL: mydomain.com
SalaX client URL: chat.mydomain.com
Admin panel URL: admin.mydomain.com
Homeserver URL: matrix.mydomain.com
Identity server URL: im.mydomain.com (on old installation it was sshsn-identity.xxx.xxx)
Homepage URL: share.mydomain.com( for some installations it was home.xxx.xxx)
Conference URL: conference.mydomain.com
Turn URL: turn.mydomain.com