Technical Support for a 1C-Bitrix Website
After launch, a website does not maintain itself. Components break after core updates, integrations fail when partner APIs change, garbage data accumulates in b_stat_adv_guest, disk space runs out due to uncleaned /bitrix/cache/ and /upload/ directories. Without regular intervention from a technical specialist, a site degrades within 3–6 months.
What Breaks Without Support
Core updates. Bitrix releases updates every 1–2 weeks. Clicking "update" on production without testing is a direct path to breaking custom components. A proper process is required: staging → test → production with rollback capability.
License expiry. Without an active license (b_license), the admin panel and update functionality are blocked. Timely renewal is part of support.
PHP and server software. Hosting providers periodically change PHP versions. Migrating from PHP 7.4 to 8.1 breaks deprecated functions (each(), create_function()) that may be present in older modules.
SSL certificate. An expired certificate causes browsers to immediately refuse to open the site.
Typical Support Tasks
| Task | Frequency | Effort |
|---|---|---|
| Availability and response monitoring | Continuous (automated) | — |
| Bitrix core update | 1–2 times per month | 1–2 hours |
| Cache and old file cleanup | Once per month | 30 min |
| SSL check and renewal | Scheduled | 30 min |
| PHP error fixes (logs) | As needed | 30 min – 4 hours |
| Backups and restore verification | Weekly | 30 min |
Monitoring and Incident Response
Availability monitoring is handled via Uptime Robot, Zabbix, or Bitrix Site Monitor. An alert fires when the site is unavailable or returns 5xx responses. Critical incidents (site down, payment system not working) require a response within 1 hour.
For tracking PHP errors — regular review of /var/log/php-fpm/ or the BX_DEBUG module. Error logging can be enabled in Bitrix via php.ini: log_errors = On, error_log = /path/to/bitrix_error.log.
Cache Management
Bitrix cache is stored in /bitrix/cache/ and in memcache/Redis (if configured). An overgrown disk cache (> 10 GB) slows down the site on systems with slow I/O. Periodic cleanup via the admin panel: Settings → Performance → Clear Cache, or via CLI:
php -f /var/www/bitrix/bitrix/modules/main/tools/cron_events.php
What Is Included in Technical Support
- Availability monitoring with alerts on incidents
- Scheduled Bitrix core updates via a staging environment
- PHP error fixes and remediation of post-update regressions
- SSL control, disk quota monitoring, cache and temporary file cleanup
- Backups with restore verification
- Bitrix license renewal tracking