Updating the Bitrix core breaks sites more often than admitted. Not because the core is bad, but because most custom code violates the principle "don't touch the core": edits in bitrix/modules/, direct calls to deprecated functions, reliance on internal component structure. The update reveals this debt.
We have 10+ years of experience updating sites on 1C-Bitrix — from simple online stores to portals with custom modules and 1C integrations. We know which errors are typical and how to prevent them. If an update is done without preparation, the site can be down for hours or days — loss of orders and reputation. The right approach is audit, staging, phased testing. We guarantee operability after the update: each stage is documented, custom code is adapted, you receive a checklist and a plan for future updates. The probability of failure is reduced by 90% compared to a self-performed update.
Why does the update break the site?
Direct edits to core files. bitrix/modules/catalog/install/components/bitrix/catalog.element/templates/.default/template.php — manually edited. After the update — overwritten with the original. Anything inside /bitrix/ that was modified is lost.
Deprecated functions. Every few versions, Bitrix declares functions deprecated and eventually removes them. Calling CIBlockElement::GetList() with incorrect parameters may behave differently than before. Calling a removed method — Fatal Error.
Changes in module APIs. The sale module was seriously reworked: the old API (CSaleOrder::Add) coexists with the new one (Bitrix\Sale\Order), but behavior in edge cases may differ.
Custom modules from Marketplace. If the module developer hasn't updated it for the new core version — after the update the module may not work.
How do we conduct the update?
We use a refined process that minimizes risks.
- Code audit. Check for edits inside
/bitrix/ (via git diff or find /bitrix -newer /bitrix/bitrix_version.php -type f), calls to deprecated functions (grep on local/), and Marketplace module compatibility.
- Deploy staging. Full copy of production with the same PHP version, external integrations disabled.
- Update on staging. Use the console tool
/bitrix/bin/console update — this removes time execution limits.
- Testing. Go through critical scenarios: homepage, catalog, product card, cart, checkout, personal account, admin panel. Check error log.
- Deploy to production. In maintenance mode, after full testing. Check logs again.
| Stage |
Duration |
| Audit and preparation |
0.5–1 day |
| Update on staging |
0.5–2 days |
| Testing |
0.5–2 days |
| Deploy to production |
1–2 hours |
What is included in the work?
After the update, you receive:
-
Full report on changed files and code adaptation.
- Checklist for site functionality verification.
- Plan for subsequent updates with recommended frequency.
- Guarantee on the operability of critical functions for 30 days.
- Consultation on further version support.
Why trust us with the update?
We are certified 1C-Bitrix specialists with 10+ years of experience and 500+ successful updates. Compared to self-updating, our approach reduces downtime by 2–3 times and eliminates typical errors.
| Criterion |
Self-update |
Our service |
| Code audit |
Often skipped |
Mandatory step |
| Staging |
Rare |
Always |
| Testing |
Surface-level |
Full scenario coverage |
| Guarantee |
None |
30 days |
| Failure risk |
High |
Minimal |
Preventing a single crash after an update can save you hundreds of thousands of rubles in emergency recovery. Contact us — we will assess your project and offer a timeline and cost individually.
Typical errors during update
- Direct edits in
/bitrix/ — overwritten during update.
- Using deprecated functions —
CIBlockElement::GetList() with incorrect parameters.
- Marketplace module incompatibility — developer hasn't released an update.
Timelines
| Situation |
Timeline |
| Regular update (gap up to 3 months) |
1–2 days |
| Update after 6–12 months of inactivity |
3–5 days |
| Update with 1.5–2 year gap |
1–2 weeks |
| Update with 3+ year gap + custom code |
2–4 weeks |
The main variable is the amount of custom code that needs adaptation. A site on standard components with code in local/ is easier to update than a site with core edits and five-year-old custom modules.
Official 1C-Bitrix update guide confirms the need for custom code audit and staging testing. We strictly follow these recommendations.
Get a consultation — contact us, we will assess your project and offer a timeline and cost individually. Order an update with a 30-day guarantee.
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.
