A .htaccess change took the site down
A rewrite rule pasted from a forum, a directive from a module that is not loaded, or stray Windows line endings in an uploaded file.
Working rules, safely tested
Working with Apache?
Most Apache servers that reach us have been edited by half a dozen people over the years, with rewrite rules layered on top of rewrite rules that nobody remembers writing. We read what is actually there and sort it out without starting over.
What it is
The Apache HTTP Server is an open-source web server first released in 1995 by the Apache Group, which later became the Apache Software Foundation. Its name comes from the phrase 'a patchy' server, because the early code was a collection of patches applied to the older NCSA HTTPd project.
It is modular, with features such as mod_rewrite, mod_ssl, mod_proxy and mod_security loaded as needed, and it has long been the default web server on most Linux distributions and shared hosting plans. It still powers a large share of the PHP sites on the internet, especially anything built on the classic LAMP stack.
Apache can run in several multi-processing modes: the old prefork model that pairs with mod_php, the threaded worker model, and the modern event model that handles more concurrent connections per process. Per-directory configuration through .htaccess files is both its best-known feature and the source of most of its support calls.
The honest version
No technology is all upside. This is where Apache earns its place and where it tends to cause trouble.
Sound familiar?
The Apache problems that bring people to us, and what you have once each one is fixed.
A rewrite rule pasted from a forum, a directive from a module that is not loaded, or stray Windows line endings in an uploaded file.
Working rules, safely tested
Rewrite rules fighting each other across nested .htaccess files, or conditions that worked on the old host but not the new one.
Redirects audited and consolidated
A port already held by another service, a bad SSL certificate path, or a syntax error introduced by the last edit before the reboot.
Back up, with a sensible restart
Apache 2.2 access rules that the new 2.4 authorisation framework no longer understands, often spread across dozens of virtual hosts.
Config brought up to 2.4
Default MPM settings on a server that has long since outgrown them, with requests queued behind slow database calls.
MPM tuned to the real workload
A web application firewall rule set that is catching real users along with the attackers, with no record of who tuned it last.
Rules tuned, false positives cleared
Old certificate chain directives, weak ciphers, and no HTTP/2, usually on a host that has been upgraded underneath the configuration.
Modern TLS with a clean grade
Dozens of sites on one server with overlapping aliases, forgotten test hosts and includes pointing at files that no longer exist.
Virtual hosts documented and tidy
What we do
Call us for one broken redirect, or hand us the whole server.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Almost always a directive that refers to a module which is not loaded, a syntax mistake in a rewrite rule, or Apache 2.2 access rules on a server that now runs 2.4. The server log names the exact file and line, which is where we start.
Yes, when it makes sense. We translate the rewrite rules, replace .htaccess with server blocks, and test the new setup in parallel before changing DNS. Some sites are better off with Nginx in front of Apache instead.
The main change is in access control: Order, Allow and Deny are replaced by the Require directive. We work through each virtual host and .htaccess file, test the result against real URLs, and only then swap the running config.
Usually rewrite rules in parent and child directories overriding each other, redirects configured in two places at once, or browser caching holding onto an older response. We trace the request from the first hop to the final page and fix whichever link in the chain is wrong.
Yes. We read the error log, find the directive or port that is causing the failure, and bring the service back. If a configuration change caused it, we also leave you with a copy of the previous config saved.
Estimates are free. Send over the httpd.conf or .htaccess and the error log you see, and we come back with a scope before touching the server.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: