How to fix "Could not reliably determine the server’s fully qualified domain name" warning in Apache

When starting or restarting the Apache web server, you might come across a warning message: “Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.” Although this warning does not impede the functioning of Apache, it can be unsettling for system administrators who prefer a warning-free startup.

This warning arises because Apache attempts to deduce the fully qualified domain name (FQDN) of the server and fails. The FQDN is a complete domain name for a computer or host and is used by Apache for various operations. Not defining the FQDN results in Apache using a fallback address, often 127.0.1.1.

Fortunately, addressing this warning is straightforward. You simply have to set the ServerName directive in Apache's configuration file. Different distributions might have varying paths for Apache's main configuration file, but the process remains consistent.

Steps to fix the ServerName warning in Apache:

Open the Apache main configuration file using your preferred text editor.
```
$ sudo vi /etc/apache2/apache2.conf
Password:
```
Related: Location for Apache main configuration file
Append the following line at the end of the file, replacing “your-server-name” with your server's FQDN or IP address.
```
ServerName your-server-name
```
Save and close the file.
Test the configuration for any syntax errors.
```
$ sudo apache2ctl configtest
```
If the output displays “Syntax OK”, proceed to the next step. Otherwise, correct any indicated errors and retest.

Restart or reload the Apache service to apply the changes.

$ sudo systemctl restart apache2 #Ubuntu, Debian, openSUSE, and SLES
$ sudo systemctl restart httpd #CentOS and Red Hat

Start or restart the Apache service again and ensure the warning message no longer appears.
```
$ sudo systemctl start apache2
```

If the warning persists, ensure the ServerName directive has been added to the correct configuration file and is correctly formatted. Once you've successfully addressed the warning, Apache will operate with the defined FQDN, leading to smoother and more predictable server behavior.

Author: Mohd Shakir Zakaria
Mohd Shakir Zakaria is an experienced cloud architect with a strong development and open-source advocacy background. He boasts multiple certifications in AWS, Red Hat, VMware, ITIL, and Linux, underscoring his expertise in cloud architecture and system administration.

Discuss the article:

Comment anonymously. Login not required.