Apache not working

Updated 11 October 2026

Short answer

Apache's error log is the first place to look; Apache's own documentation calls it the most important log file. If Apache won't start at all, run apachectl configtest: it finds config syntax errors without starting the server. If Apache runs but pages fail, the usual causes are a broken .htaccess file (500 errors), file permissions (403), or something else already using port 80 or 443.

What's the problem

The site won't load, Apache won't start or restart, or pages show 500, 403 or 503 errors from Apache.

Why it happens

  • A config syntax error, so Apache refuses to start.
  • A broken .htaccess file, a common cause of 500 errors, especially on WordPress sites.
  • Port 80 or 443 already in use by another program, such as Nginx or a second Apache.
  • A module that isn't enabled, such as the rewrite module needed for pretty URLs.
  • File permissions stopping Apache reading your files (403).
  • Apache ran out of workers under load.

How to fix it

  1. Read the error log. Its location is set by the ErrorLog line in Apache's configuration; on most Linux servers it's under /var/log/. On shared hosting, find "Error log" in the control panel.
  2. If Apache won't start, run apachectl configtest and fix the line it reports.
  3. For 500 errors, rename .htaccess temporarily to see whether it's the cause.
  4. Check nothing else is using the port (sudo ss -tlnp | grep ':80').
  5. Check required modules are enabled, such as mod_rewrite.
  6. Restart Apache once the config test passes.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; uptime checked every 5 minutes, with an email when the site goes down and when it is back. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when; recent deploys and account changes, with their times. It can't log in to your server, so memory, disk and process problems show up in your host's dashboard and logs.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. Apache HTTP Server: Log Filesofficial docsThis is the place where Apache httpd will send diagnostic information and record any errors that it encounters in processing requests. It is the first place to look when a problem occurs
  2. Apache HTTP Server: Configuration Filesofficial docsYou can check your configuration files for syntax errors without starting the server by using apachectl configtest or the -t command line option.
  3. WordPress: Common WordPress errorsofficial docsThe most likely issue is a corrupted .htaccess file.
  4. Apache HTTP Server: Log Filesofficial docsThe server error log, whose name and location is set by the ErrorLog directive, is the most important log file.

Related

Nginx error Nginx's error log names the problem. 502 means the app behind Nginx is down; 504 means it's too slow; a failed reload means a config typo. Run nginx -t first. 500 Internal Server Error Your server hit an error it didn't handle. The cause is in the server's error log: usually a code bug, a bad config change, a failed plugin or a lost database. 403 Forbidden The server understood the request but won't allow it. Usually file permissions, a missing index page, or a firewall or security rule blocking the visitor. Server crash Find out what crashed (the whole machine, or just your app or database), then read the logs from just before. Most crashes are memory, disk, or a code change.

Preventionlabs is independent and not affiliated with Apache. Product names are used only to describe the problem.

← All of Server