Push and Pull Setup in Bitrix: Eliminate Chat and Notification Delays

Online chat only updates on page reload. Notifications about new orders arrive minutes late. The live feed in Bitrix24 corporate portal doesn't update in real time due to a missing configured Push and Pull module. All these are consequences of not having Push and Pull set up. Our team with 10 years of experience encounters this regularly. Setting up this module is one of the first tasks when launching projects with online chats, notifications, or corporate portals. Without it, the system loses responsiveness, and users lose convenience. We've completed over 70 projects configuring Push and Pull for e-commerce stores and corporate portals, and in 95% of cases the problem is solved within 1-3 days. Proper configuration of Bitrix notifications directly depends on Push and Pull operation.

How the Push and Pull Module Solves Delay Problems

Push and Pull provides real-time two-way communication between the server and browser. This allows instant delivery of chat messages, order notifications, feed updates, and other events without page reload. The pull module uses several transports: WebSocket, Long Polling, and Server-Sent Events. WebSocket offers minimal latency of 1–5 ms but requires a separate Node.js server. Long Polling works via PHP and doesn't require additional services. SSE is an alternative for one-way transmission. Push and pull web technologies (WebSocket and Long Polling) are the foundation of instant delivery.

Comparison of transports:

Wikipedia: WebSocket | Wikipedia: Long Polling

WebSocket reduces latency by 40 times compared to Long Polling, which is especially important for high-load projects. In one e-commerce project with 5000 online users, after configuring WebSocket, the delay dropped from 2 seconds to 5 ms — 400 times faster.

Why a Project Loses Real-Time Without Push and Pull

• Delayed notifications. Without Push and Pull, notifications about new orders only arrive after page reload or by agent schedule. This is critical for e-commerce: managers lose reaction time.
• Non-updating online chat. Customers complain that messages don't arrive in real time — they have to reload the page. This reduces conversion and support quality.
• Server load. Long Polling creates many hanging connections. Without proper Nginx configuration, the server may fail under peak load.

How We Configure Push and Pull: A Case with 5000 Users

We use a proven stack: PHP 8.1+, Nginx with optimized parameters, Node.js 18+ for WebSocket. Configuration includes:

1. Module installation. Download the push and pull module from Marketplace and install it into the system.
2. Basic settings. In the administration panel, specify the push server address and security key.
3. Nginx configuration for Long Polling. Increase worker_connections to 8192, disable buffering. Example config:

location ^~ /bitrix/pub/ {
    proxy_pass http://127.0.0.1:9000;
    proxy_http_version 1.1;
    proxy_set_header Connection "";
    proxy_read_timeout 25;
    proxy_send_timeout 25;
    proxy_buffering off;
    proxy_cache off;
}

4. Launch Node.js server (if WebSocket is required). Set up auto-start via systemd.
5. Testing. Verify notification delivery by simulating peak load (up to 1000 simultaneous connections).

In one e-commerce project with 5000 online users, we encountered worker_connections overflow. After increasing limits and enabling epoll, the system steadily handles peak load without connection loss.

What's Included: From Audit to Testing

• Audit of current server and Bitrix configuration.
• Installation and configuration of the Push and Pull module.
• Setup of Node.js push server (if WebSocket is required).
• Optimization of Nginx and PHP-FPM for long connections.
• Testing with simulated peak load.
• Documentation for maintenance and monitoring.

Setup time — from 1 to 3 days depending on complexity. Cost is calculated individually after analyzing your project. Certified 1C-Bitrix specialists guarantee stability. Order setup — get an engineer consultation. Contact us today.

How to Avoid Common Configuration Errors

How to Verify the Push and Pull Module Works

Open browser console (F12) and go to the Network tab. Perform an action that should trigger a notification (e.g., send a chat message). If you see requests to /bitrix/pub/ with type long-poll or WebSocket, the module works. If there are no requests, check the admin panel settings and push server status.

Configuring the Push and Pull module is a critical step for any 1C-Bitrix project that requires real-time functionality. Our team with 10 years of experience is ready to help. Contact us for a consultation — we will select the optimal configuration for your project.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.