1C-Bitrix Turnkey Installation and Initial Setup

After purchasing a 1C-Bitrix license, the distribution needs proper deployment. Incorrect initial server or kernel configuration only becomes apparent months later—the site slows down or fails under peak load. PHP or database errors cause crashes during 1C data exchange and slow page loading. To avoid this, order 1C-Bitrix turnkey installation from us—with guaranteed correct configuration.

Real case: a client with a catalog of 15,000 products faced timeouts a month after deployment. The cause was default PHP settings and agents in web mode. After reconfiguration, load time dropped from 5 seconds to 0.8, and 1C data exchange stopped failing. Such problems occur in 6 out of 10 projects if initial setup is neglected.

Why Is Proper Initial Setup Necessary?

Typical situation: a developer installs Bitrix with default PHP settings, forgets to enable caching, and leaves agents in web mode. The site works for the first few weeks, but after adding a catalog of 10,000 products, timeouts begin. CommerceML import aborts, pages take 5 seconds to load. This can only be prevented at the installation stage by establishing the correct configuration. Additionally, incorrect PHP session or encoding settings can cause errors in the cart and authorization—issues that are hard to diagnose later.

What Are the Server Requirements and PHP Configuration?

Minimum stack for production: PHP 8.1+, MySQL 8.0 or PostgreSQL 13+, Nginx + PHP-FPM. Apache is slower—Nginx serves up to 2x more concurrent connections. Critical PHP settings:

Official 1C-Bitrix documentation recommends using Nginx as the primary web server (Wikipedia: Nginx). Also important is correct PHP-FPM pool configuration: pm.max_children should be calculated based on available memory. For details, see 1C-Bitrix System Requirements.

Turnkey Installation and Initial Setup Process

1. Analysis: We study the load, catalog structure, data volume, and integrations (1C, payment gateways, delivery services).
2. Configuration Design: We choose the optimal stack (software versions, caching server, database settings). For typical projects, we use bitrix-env—a script that deploys Nginx, PHP-FPM, MySQL, and memcached with Bitrix-optimized settings in 25 minutes. Compared to manual setup (2-4 hours), bitrix-env is 5 times faster.
3. Installation: We unpack the distribution, run the wizard, create an admin user, and select the edition.
4. Initial Configuration: We configure the main module (time zone, UTF-8 encoding, email notifications), enable caching on memcached or Redis, move agents to cron, set paths for temporary files, and run the system update.
5. Testing: We check page load speed, agent operation, 1C data exchange, and caching correctness. We perform load testing with ab or siege.
6. Deployment and Documentation: We hand over access, configuration files, and an operating manual. We train the administrator on basic operations.

Agents on Cron — Guarantee of Stability

By default, agents execute on page visits. This is unstable: under high load, agents may not keep up, and without visitors, tasks (CommerceML import, email sending) are delayed. Moving to cron ensures scheduled execution, even when the site is not visited.

Example PHP configuration for Bitrix (fragment):

memory_limit = 512M
max_execution_time = 120
realpath_cache_size = 4096K
opcache.memory_consumption = 256
upload_max_filesize = 128M
post_max_size = 128M

This set of parameters addresses 90% of performance issues at the start. Also configure agents in cron: create a crontab task calling /usr/bin/php /path/to/bitrix/modules/main/tools/cron_events.php.

What's Included in the Service

• Detailed configuration documentation with all settings and rationale
• Administrator training session (up to 2 hours) covering basic operations
• 30 days of post-installation support for any critical issues
• Access to all configuration files and credentials
• Performance test report before and after setup

Comparison of Installation Methods: bitrix-env vs Manual

For 8 out of 10 projects, bitrix-env is faster and more reliable. Manual installation is justified for non-standard architectures (clustering, custom modules).

Timelines and Cost

Installation time on a prepared server is 1-2 days. If the server is set up from scratch, it takes 3-5 days. Cost is calculated individually based on project complexity—typically ranging from $800 to $2,500. Clients who invest in professional setup report 30-40% fewer support issues later, saving an average of $3,000–$5,000 in future fixes. You receive a platform ready for peak loads, saving on future support. Contact us for a project assessment—we will prepare a commercial proposal with exact timelines. Get a consultation by phone—we will explain which parameters are critical for your specific catalog.

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. 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.