Configuring Bitrix24 On-Premise Updates
Updating the on-premise version of Bitrix24 on production can lead to downtime. A custom module becomes incompatible with the new kernel version — a typical situation. Without preparation, the update breaks customizations and disrupts integrations. We, certified specialists with over 7 years of experience, have developed a procedure that reduces downtime by 90% and guarantees stability. During this time, we have completed more than 50 projects for configuring Bitrix24 On-Premise updates. Custom code created as part of Bitrix24 development must be stored in /local/.
What risks does an uncontrolled update carry?
Major Bitrix24 releases perform database migrations via \Bitrix\Main\Application::getConnection()->queryExecute(). If system tables b_* contain non-standard fields from custom modules, the migration will damage data. Security patches are usually safer, but without testing on staging, you risk losing integrations with 1C, CDEK, or CRM. Modules from the Marketplace sometimes reset settings during updates — especially critical for business process management modules.
How to choose an update strategy?
Auto-updates should only be enabled for security patches (flag SECURITY = Y). Major releases should be applied manually after testing. Compare update types in the table:
| Update Type | Change Scope | Risk for Custom Code | Testing |
|---|---|---|---|
| Patch | Point files | Low (if kernel not modified) | Recommended |
| Release | Files + DB schema | High (migrations conflict) | Mandatory on staging |
Automatic application of patches via agent is 10 times faster than manual update. For major releases, manual control remains mandatory. Average downtime for manual update without preparation is 4 hours; with our procedure it reduces to 30 minutes.
How to set up auto-updates on production?
In the section /bitrix/admin/update_system_partner.php, you can enable automatic retrieval of updates on a schedule. It is safer to use an agent that checks for updates every 24 hours and installs only critical patches.
// Agent checks for updates every 24 hours CAgent::AddAgent( "CUpdateClient::CheckUpdates();", "main", "N", 86400, "", "Y" ); Additionally, configure error notifications to quickly identify issues.
Step-by-step update procedure on production
Step 1: Backup. Before any update, back up files and database. Use the built-in module or console:
mysqldump -u bitrix -p bitrix24_db > /backup/bitrix24_$(date +%Y%m%d_%H%M).sql tar czf /backup/bitrix24_files_$(date +%Y%m%d_%H%M).tar.gz /var/www/html --exclude=/var/www/html/upload Step 2: Test on staging. If a staging server exists (and it should), apply the update there and run tests:
- Custom components in
/local/components/ - Custom handlers in
/local/php_interface/init.php - Modules from
/local/modules/ - Integrations with external systems (1C, CRM, OFD)
Step 3: Maintenance mode. Before updating on production, enable maintenance mode:
<?php // /bitrix/.maintenance.php header('HTTP/1.1 503 Service Unavailable'); header('Retry-After: 3600'); include '/path/to/maintenance_page.html'; exit; In nginx, intercept all requests and show the maintenance page. Step 4: Apply the update. Via /bitrix/admin/update_system.php or console handler.
Step 5: Post-update check. Check critical pages: home, catalog, product card, cart, checkout, personal account, admin panel. Review php-fpm and nginx logs for new errors.
Post-update check list
- Main page loads without errors
- Product catalog displays correctly
- Product card opens and shows prices/stocks
- Cart adds and removes items
- Checkout completes successfully
- Personal account works
- Admin panel is accessible
- php-fpm and nginx logs have no new errors
Typical errors and how to avoid them
| Error | Consequence | Solution |
|---|---|---|
| Kernel modification | Overwritten on update | All custom code in /local/ |
| Skipping testing | Production downtime | Use staging server |
| Ignoring changelog | Module settings reset | Read changelog before update |
In 80% of our clients, issues were identified precisely on staging.
What is included in update configuration?
As part of the service, we perform:
- Audit of current configuration and custom code
- Setting up automatic updates for security patches
- Configuring agents and notifications
- Creating a staging server (if absent)
- Developing backup procedures
- Testing updates on staging
- Documenting the process and checklists
- Training administrators
The result is a stable system with minimal downtime during updates. Contact us for a consultation.
Why trust professionals with updates?
An uncontrolled update can lead to hours of downtime and data loss. We guarantee stability after the update: certified Bitrix specialists, licensed software, over 7 years of experience, and more than 50 successful projects. We document every step — you always know what changed.
Get a consultation on configuring updates for your Bitrix24. We will conduct an audit of your current configuration and offer the optimal solution considering your stack and custom customizations. Request a project evaluation — we will respond within one day.
Additionally, the official Bitrix24 update documentation recommends testing on staging for all major releases. Read more in the official guide.