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:
| Transport | Latency | Requirements | Recommendations |
|---|---|---|---|
| WebSocket | 1–5 ms | Node.js server | For high-load projects |
| Long Polling | 50–200 ms | PHP-FPM + Nginx | For medium and small projects |
| SSE | 5–20 ms | Node.js or PHP | For one-way events |
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:
- Module installation. Download the
push and pullmodule from Marketplace and install it into the system. - Basic settings. In the administration panel, specify the push server address and security key.
- Nginx configuration for Long Polling. Increase
worker_connectionsto 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; } - Launch Node.js server (if WebSocket is required). Set up auto-start via systemd.
- 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
| Problem | Solution | Time |
|---|---|---|
| Error 502 during channel connection | Check systemctl status push-server and enable auto-start | 30 min |
| Delays with long polling | Increase proxy_read_timeout to 25 seconds | 15 min |
| worker_connections overflow | Increase limits in Nginx and ulimit -n 65535 | 30 min |
| Message loss after PHP-FPM restart | Run agent manually or configure cron | 20 min |
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.