How to test Apache configuration

Testing the Apache configuration before a reload catches broken directives, bad include files, and typo-driven outages while the current worker processes are still serving traffic. A quick syntax pass turns a configuration edit into a controlled checkpoint instead of a risky live experiment.

The control wrapper apache2ctl or apachectl asks the underlying httpd binary to parse the main configuration file and every included file without replacing the running server. The result reports the first file and line that fails parsing, and the same test is also available through the -t option.

Examples below use the Debian and Ubuntu layout with /etc/apache2/, the apache2 systemd unit, and the apache2ctl wrapper. Other distributions usually expose the same check as apachectl -t or httpd -t, and a clean syntax result still needs a reload plus a service or HTTP check because the parser does not catch every runtime problem.

Steps to test Apache configuration:

Open a terminal session with an account that can use sudo.
Open the Apache configuration file or virtual host file that was changed.
```
$ sudo vi /etc/apache2/sites-available/example.com.conf
```
Common edit locations on Debian and Ubuntu include /etc/apache2/apache2.conf, /etc/apache2/sites-available, and /etc/apache2/conf-available.

Related: How to locate Apache configuration files
Run the Apache syntax test.
```
$ sudo apache2ctl configtest
AH00526: Syntax error on line 1 of /etc/apache2/conf-enabled/zz-broken.conf:
Invalid command 'ServerNmae', perhaps misspelled or defined by a module not included in the server configuration
```
apache2ctl configtest and apache2ctl -t perform the same syntax check. Use sudo apachectl -t or sudo httpd -t on platforms that ship those control names instead.

Related: Apache binary name for different distribution
Use the first reported file and line number to locate the failing directive or include.

If the output suggests that the Apache error log may have more information, inspect sudo journalctl --unit=apache2 --no-pager --lines=20 on systemd hosts or the platform error log path listed in How to locate Apache configuration files.
Correct the referenced directive, enable the missing module, or remove the bad include before testing again.
Re-run the syntax test until it returns a clean result.
```
$ sudo apache2ctl configtest
Syntax OK
```
The AH00558 message about the server's fully qualified domain name is a warning, not a syntax failure. Set a global ServerName to silence it when needed.

A clean syntax test does not prove that ports are free, certificates exist at the configured paths, or backend services are reachable. It only confirms that the loaded configuration parses successfully.
Reload Apache to apply the validated configuration without dropping active connections.
```
$ sudo systemctl reload apache2
```
When systemd is not managing the service, use sudo apache2ctl graceful or the platform-equivalent reload command. On Red Hat-family systems, the unit name is commonly httpd.

Related: How to manage the Apache web server service
Confirm that Apache is still active after the reload.
```
$ sudo systemctl is-active apache2
active
```
If the service does not return active, inspect the journal immediately before retrying the reload.

Related: How to manage the Apache web server service

Confirm that the server still answers HTTP requests after the reload.

$ curl -I -sS http://127.0.0.1/
HTTP/1.1 200 OK
Date: Wed, 08 Apr 2026 04:12:54 GMT
Server: Apache/2.4.58 (Ubuntu)
Last-Modified: Wed, 08 Apr 2026 04:12:52 GMT
ETag: "29af-64eeb1d18f48f"
Accept-Ranges: bytes
Content-Length: 10671
Vary: Accept-Encoding
Content-Type: text/html

Use the site hostname or a Host header that matches the active virtual host when localhost is not served by the configuration being tested.