Server Network Requirements
The information in this section is intended for system administrators who are configuring your company's network and server hardware.
Rox.Chat Server requires the following parameters and accesses to be configured:
| Parameter | Value | Features |
|---|---|---|
| HTTPS port | 443 | Configure access on the 443 TCP port from the outside. If the organization's site is running on HTTPS, application requests will also go to the Rox.Chat Server on this port (recommended over HTTP/80). Rox.Chat APIs/SDKs also run over HTTPS/443. |
| HTTP port | 80 | Configure access on the 80 TCP port from the outside. If your site is running on HTTP, requests to the Rox.Chat Server will go on HTTP/80 (not recommended!). |
| Chat Backend | 8260 (default) | This TCP port must be free and open internally (on localhost) on the server, no external access is required. You can choose any other port, but then Chat Backend must be reconfigured. |
| DBMS port | 3306 (default for MySQL) | Can be set to any other port. |
| SSL/TLS certificate | If you choose to use HTTPS, you will need an SSL/TLS certificate for your domain. Among other options, the certificate itself can be placed on your balancer, after which the traffic will be redirected to another domain name over HTTP or HTTPS | |
| DNS entry | e.g. roxchat.yourdomain.com or myaccount.rox.chat |
The Rox.Chat server can be configured to run on a host in your domain or in the rox.chat domain. In both cases, the domain name of the server must be of the third level. Without a domain name Rox.Chat Server will not work. |
| SMTP(S): server IP, port, login-password | To send e-mail messages you need details of the server available via Secure SMTP - for example, Mailgun. The value must not be an empty string. |
Monitoring, automatic backup/restore, load balancing (recommended) can be integrated on customer's request.