Installing Bitrix24 Self-hosted

The setup:

 -----------------------                                   ---------------------------------------------------
| nginx: 0.0.0.0:80     | -> /bitrix/sub|/bitrix/subws -> | node server.js --config push-server-sub-80XX.json |
 -----------------------                                   ---------------------------------------------------

 -----------------------                     ---------------------------------------------------
| nginx: 127.0.0.1:8895 | -> /bitrix/pub -> | node server.js --config push-server-pub-90XX.json |
 -----------------------                     ---------------------------------------------------

Nginx proxies query to push service of selected type. Message getting queries (for example, sub) are public and proxied from standard ports 80/443. Publication queries (pub) are available only from internal server address.

Nodejs processes are split into two types:

1. Processes responsible for connecting user to selected channel and message reception. Listen to ports: 8010-8015;
2. Processes responsible for sending message to channel. Listen to ports: 9010-9011.

To start Push-server we need:

• nodejs & npm ;
• service and its modules archive.

For installation we require Python or a make utility:

zypper install python3 make wget -y

Execute the following actions:

1. Download archive from repository repos.bitrix24.com

   wget https://repos.bitrix24.com/vm/push-server-0.2.2.tgz

   or the push-server-0.2.2.tgz archive from site and place it into directory /opt. Execute the installation:

   su -
   cd /opt
   npm install --production ./push-server-0.2.2.tgz
   

   Installation will finish with string:

   + push-server@0.2.2
   added 65 packages from 78 contributors and audited 65 packages in 45.77s
   

2. Execute (exclusively for convenience):

   su -
   ln -sf /opt/node_modules/push-server/logs /var/log/push-server
   ln -sf /opt/node_modules/push-server/etc/push-server /etc/push-server
   

3. Copy service files and the main configuration:

   su - 
   cd /opt/node_modules/push-server
   cp etc/init.d/push-server-multi /usr/local/bin/push-server-multi
   cp etc/sysconfig/push-server-multi  /etc/sysconfig/push-server-multi
   cp etc/push-server/push-server.service  /etc/systemd/system/
   ln -sf /opt/node_modules/push-server /opt/push-server
   

4. Create temporary directory:

   echo 'd /tmp/push-server 0770 wwwrun www -' > /etc/tmpfiles.d/push-server.conf
   systemd-tmpfiles --remove --create
   

   Edit config file /etc/sysconfig/push-server-multi. The following parameters must be corrected/added:

   • USER/GROUP - user that launched service;
   • SECURITY_KEY - secret key for connection signature between customers and push server;
     Note: Key length doesn't matter. The key can use only Latin letter and numbers, special characters are prohibited. But, be advised, that a too short of a key is unsafe. It can be generated as follows:

     cat /dev/urandom |tr -dc A-Za-z0-9 | head -c 128

   • RUN_DIR - director for process PID file storage.

   Example of parameter settings:

   GROUP=www
   USER=wwwrun
   SECURITY_KEY="SECURITYKEY123456"
   RUN_DIR=/tmp/push-server
   REDIS_SOCK=/var/run/redis/default.sock
   

5. Each nodejs process is launched as separate process. Generate the configs:

   /usr/local/bin/push-server-multi configs pub
   /usr/local/bin/push-server-multi configs sub
   

   Generated configs in the format json push-server-sub-80XX.json
   push-server-pub-90XX.json will be located in this directory: /etc/push-server/.

6. Update the user and path to script in the service config file /etc/systemd/system/push-server.service:

   [Service]
   User=wwwrun
   Group=www
   ExecStart=/usr/local/bin/push-server-multi systemd_start
   ExecStop=/usr/local/bin/push-server-multi stop
   ...
   

7. Update access permissions for directory with logs:

   chown wwwrun:www /opt/node_modules/push-server/logs /tmp/push-server -RH
   

8. Reconfigure:

   systemctl daemon-reload
   

9. Start the service:

   systemctl --now enable push-server
   

10. Go to push module config (site settings) and enable local push server (latest version). Additionally, indicate SECURITY_KEY parameter, configured previously above in the file /etc/sysconfig/push-server-multi.