Bitrix24 On-Premise Setup & Configuration — Full-Cycle Service

Picture this: you’ve purchased a Bitrix24 license, installed the distribution on your server, and within a month employees are complaining about slow performance, emails land in spam, and 1C integration fails. Sound familiar? We encounter this on every second project. For example, on a recent project with 30 users, pages took 12 seconds to load after installation without Redis configuration — resulting in a 40% productivity loss. Or the case where incorrect cron settings prevented agents from sending notifications, causing managers to miss a deal. Proper configuration of Bitrix24 On-Premise is not just running the setup wizard. It’s a comprehensive set of tasks: from choosing the server stack to configuring agents and caching. With 10+ years of experience and certified Bitrix24 partner status, we’ve configured over 50 on-premise installations, each requiring an individual approach. We guarantee results or your money back within 30 days. Get a consultation with an engineer — we’ll check your configuration and propose optimizations.

Bitrix24 On-Premise Configuration: Complete Checklist

Infrastructure Requirements

Minimum requirements for teams up to 50 users:

For 100+ users, clustering is required — that’s a separate topic. However, even at 50 users, it’s important to place the DBMS on a separate server.

Initial Configuration After Installation

After installing the distribution and completing the setup wizard, go through this mandatory checklist.

How to configure SSL/TLS?

Bitrix24 On-Premise without HTTPS is unforgivable. Use Certbot + Let’s Encrypt or a corporate certificate. Set up a forced HTTP → HTTPS redirect in the nginx configuration.

How to optimize PHP?

Critical parameters in php.ini:

memory_limit = 512M max_execution_time = 300 upload_max_filesize = 100M post_max_size = 100M opcache.enable = 1 opcache.memory_consumption = 256 

How to configure MySQL/MariaDB?

Mandatory settings in my.cnf:

innodb_buffer_pool_size = 4G # ~60-70% of RAM innodb_log_file_size = 512M max_connections = 200 query_cache_type = 0 # disable, use Redis instead 

How to configure caching?

Connect Redis or Memcached for sessions and data cache. Without caching, the system runs 3–5 times slower under load. Redis is the optimal choice. According to official documentation, caching with Redis boosts performance up to 5x. Redis cache outperforms Memcached by 2x in transaction throughput. Our optimization techniques ensure peak performance.

Agents and Cron: Why This Is Critical

Bitrix24 On-Premise uses agents for background tasks: sending notifications, synchronizing with 1C, updating the search index. If agents are not configured, the system will hang during mass operations. Set up cron-based agent execution instead of the built-in hit /bitrix/tools/cron_agents.php:

*/5 * * * * php -f /var/www/bitrix/tools/cron_agents.php 

Or use cron_events.php. Ensure the constant BX_CRONTAB_SUPPORT is defined in dbconn.php.

How to verify agent operation?

1. Check if cron is running: crontab -l.
2. Ensure BX_CRONTAB_SUPPORT is defined in dbconn.php.
3. Run a test: php /path/to/bitrix/tools/cron_agents.php.
4. Check agent logs in the Bitrix24 event log.

Integration with 1C and External Services

Exchange with 1C via CommerceML is a common point of failure. Ensure access rights to infoblocks are set correctly and exchange profiles work. For Bitrix24 REST API, use webhooks and OAuth authorization. More details in the official documentation.

Comparison of Business and Enterprise Editions

Mail Server and Notifications

On-premise does not use Bitrix24 cloud mail servers — you need to connect your own SMTP. Configuration: Settings → Mail → Outgoing Mail. We recommend not using corporate SMTP directly — set up Postfix as a relay with a reputable IP or use a transactional service (SendGrid, Unisender). Separately configure DKIM and SPF for your domain — otherwise Bitrix24 notifications will land in spam.

Updates and Maintenance

On-premise updates are performed manually or via the built-in updater. We strongly advise:

• Do not update immediately after a new version release — wait 2–3 weeks for patches to appear.
• Perform a full backup (files + DB) before every update.
• Maintain a staging server with the same version for pre-testing updates.

Updating Bitrix24 On-Premise is not just “press a button.” After major version updates, custom modifications made via bitrix/php_interface/init.php often break. Allocate time for verification and fixes.

Typical Errors and Solutions

Deliverables – What’s Included in On-Premise Configuration

• Audit of current server infrastructure
• Installation and setup of the Bitrix24 distribution
• Configuration of PHP, MySQL, web server (nginx/apache)
• Caching setup (Redis/Memcached)
• SSL/TLS configuration (Let’s Encrypt or corporate certificate)
• Mail server and DNS record setup (DKIM, SPF)
• Agent and cron configuration
• Integration with 1C (CommerceML) and external services
• Administrator training on system operation
• Technical support after launch (up to 3 months)
• Full documentation of the configuration
• Access credentials and handover

The on-premise version requires upfront investment but eliminates monthly payments, which is beneficial when scaling. Our service starts from $2,500 and can save you up to $5,000 annually compared to cloud subscription fees. Proper caching configuration reduces server resource costs by lowering CPU and DB load. Order an audit of your on-premise version — we’ll identify bottlenecks and propose optimization. Contact us for a consultation on on-premise setup and support.