What our engineers handle on Apache HTTP Server
This is the hands-on work, done by a person: the jobs the automatic tools cannot do for you.
- 1Choose and tune the MPM (event, worker or prefork) and PHP handler for your traffic
- 2Maintain virtual hosts, redirects, headers and TLS configuration
- 3Install and tune ModSecurity rules so attacks are blocked without breaking forms
- 4Read the logs to find slow requests, crawlers and attacks, and act on them
Problems we fix
Problem
The server runs out of memory under load
What we do
We check MaxRequestWorkers and PHP settings against real memory, lower or switch the model and test with traffic.
Problem
.htaccess changes break the whole site
What we do
We read the error log, fix the rule or module that is missing and restore the site, then keep the working version safe.
Problem
ModSecurity blocks legitimate customers
What we do
We find the rule that fires, tune or exclude it narrowly for that application and keep protection on for the rest.
Automatic tools, and our team for the rest
RootManage is automatic server management with every tool in one place. The tools run by themselves on a schedule and report to one dashboard. Everything they cannot do, and every emergency, is handled by our engineers by hand.
Automatic
RootManage tools, running by themselves
- Server Health agent reports load, disk use and failed login attempts to your dashboard.
- Metrics agent draws CPU, memory, disk and network charts, sampled every five minutes.
- Uptime checks check the server every minute and email you when it stops answering, and again when it recovers.
- LiteHouse runs a low-priority audit of your website at 04:00 IST and lists findings you can act on.
- Guard watches traffic for abnormal spikes and lets us block or unblock addresses. It is not an internet DDoS scrubber.
Manual, by our engineers
Everything else, and every emergency
- Hands-on work. Fixes, tuning, migrations, upgrades and the other jobs listed above on this page.
- Emergency work. A hacked site, an outage or a failed update is handled by a person who investigates and fixes it, not by a script.
- Things we do not automate. Anything the tools do not cover is done by hand, over SSH, WHM or RDP, on a login you can remove at any time.
The tools are optional, run on Linux servers and are installed by you with one command each. Every job our team does is recorded as a task in your dashboard with the details, and you get an email when it is updated.
How it works
- 1
Sign up
Create an account, choose a plan and add the server you want managed.
- 2
Install the tools
Run one command per tool. They then work by themselves and report to your dashboard. For hands-on work you give us a login you can remove at any time.
- 3
Automatic, with people behind it
The tools watch, scan and back up automatically and alert you. Our engineers do the rest by hand and handle every emergency, and you follow each task in your dashboard.
Questions about Apache HTTP Server
Is Apache or Nginx better for my site?
Both are fine. Apache suits sites that depend on .htaccess and panels like cPanel; Nginx suits high-traffic sites and proxying. We can run either, or both together.
Can you speed up an Apache server without changing hardware?
Often yes, through the right MPM, PHP-FPM settings, caching and compression. We measure before and after so you see the difference.
What does it cost to have Apache HTTP Server managed?
Managed plans start at ₹1,999 a month for one server, and Apache HTTP Server is managed as part of the server. The pricing page lists what each plan includes. If a server is already infected, the emergency cleanup is a one-time ₹9,000 job.