Nginx / Apache
Route each request to the right application
We inspect virtual hosts, HTTPS, redirects, limits and request forwarding to PHP. Changes are agreed with existing websites in mind.
- Routing and HTTPS
- Response and error logs
Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.
Administration
We configure and maintain the environment your website runs on. We examine services, resource usage and error logs, address causes of failures and agree on changes that fit the application and available resources.
Your website environment
Select a layer to see what we check. The actual environment depends on your project.
Nginx / Apache
We inspect virtual hosts, HTTPS, redirects, limits and request forwarding to PHP. Changes are agreed with existing websites in mind.
PHP / OPcache
We review version compatibility, available memory, worker queues and OPcache. Configuration follows the workload of the specific project.
MySQL / MariaDB
We investigate slow queries, locking and memory usage. Database tuning is distinguished from changes to queries and application structure.
Redis / Memcached
We review cache compatibility and data refresh rules. The caching method is chosen for the application without installing unnecessary services.
Pricing and setup
One-time configuration after diagnosis: PHP and OPcache settings, Nginx or Apache configuration, database buffers and slow query analysis. Compatible caching mechanisms are selected based on the findings. Ongoing administration is priced separately.
Measurement-led optimisation
We compare server behaviour under comparable conditions. This shows which changes help your particular website.
Choose the pages and actions to check.
Repeat the same requests after tuning.
Check memory, CPU and processing queues.
Assess the load and remaining constraints.
Record the affected website journeys.
Check compatibility and those same journeys.
The scope of work
We review web server and PHP configuration, process settings, limits and request handling.
We inspect database load, buffers and slow queries; schema or code changes are assessed separately.
We check service status, scheduled jobs and how 1C-Bitrix agents run in the server environment.
We configure notification sending and investigate errors in the available mail logs.
We agree on the data to back up, the schedule, storage location and recovery verification procedure.
We review required access permissions and agree on system component updates with compatibility in mind.
Before we begin
The available work depends on the operating system, access and provider restrictions. We review the environment first and clarify which tasks can be performed on your server.
This is a one-time server configuration for 1C-Bitrix, covering checks of PHP and OPcache, Nginx or Apache, database buffers and slow queries. The actual changes depend on diagnostics and compatibility. Website code redevelopment and additional resources are not automatically included.
The result depends on website code, database queries, external services, load and resources. After diagnosis, we explain which constraints can be addressed through configuration and which require application changes or infrastructure changes.
Some changes require service restarts or temporary access restrictions. Where necessary, we agree on the procedure and timing in advance, then check website availability and the affected functions.
Server settings can restrict some unwanted requests, but they do not replace a dedicated DDoS protection service. The service and its terms are discussed separately, taking the website's hosting arrangement into account.
Server administration brings together web server, PHP and database configuration, background tasks and outgoing mail. On a 1C-Bitrix website, these parts need to work together: a problem in one process can affect the catalogue, orders and 1C data exchange. General iT reviews the server environment in the context of the application and helps address identified technical constraints.
Server optimisation for 1C-Bitrix is based on diagnosis rather than one set of parameters applied to every project. We review OPcache settings, Nginx or Apache operation, database memory usage and slow queries. Caching and other changes are selected for compatibility and measured needs; any requirement for additional resources is discussed separately.
The next step
Tell us where the website is hosted, what is unstable and which changes you need. We will review the environment and propose the work required.