Sep
18
18
Apache2: Could not determine the server’s fully qualified domain name
If you get following error in your apache:
apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words:
sudo vi /etc/apache2/httpd.conf
followed by adding the following string:
# ServerName is specified
# to avoid warning during reload
ServerName MYSERVER
# to avoid warning during reload
ServerName MYSERVER
Share this article:
6 Comments to “Apache2: Could not determine the server’s fully qualified domain name”
Leave a comment
Sponsors
Categories
Tags
Apache
apache2
benchmark
cleanup
deb
debian
experimental
Firefox
grab them all
grabthemall
Hamachi
hamachi basic
homepost
howto
imagemagick
instsrv
Linux
Pear
Pecl
pgadmin
PHP
php5
postrgresql
profiler
realvnc
repair
screenshot
service
serviceex
sources.list
srvany
svn
symfony
tidy
tlen.pl
ubuntu
var_dump
vista
VNC
Windows
Wine
xdebug
xhtml
xp
xul
[...] Peter wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]
[...] Peter wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]
[...] Peter wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]
[...] Tony wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]
[...] Tony wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]
[...] Tony wrote an interesting post today onHere’s a quick excerptapache2: Could not determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName. The fix is to edit the conf file and add in the ServerName setting (as the error message requests). In other words: … [...]