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.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
