Localhost Apache 2 Server Warning On Ubuntu 11

19th September 2011 - 3 minutes read time

I was recently setting up a localhost environment with Ubuntu 11 and after adding all of my needed VirtualVost directives I found that I could start/restart the server but that I found the following error when trying to start the server.

user2@machine:/etc/apache2/sites-available$ sudo apache2ctl -k start
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName

To fix the problem you needed to add a simple directive to the Apache httpd.conf file. In order to access this file you'll need be have admin access, so open up a terminal window and type the following command.

sudo gedit /etc/apache2/httpd.conf

Don't worry if the file you open is empty, it is meant to be. The httpd.conf file is a user editable file that you can add directives to in order to configure your Apache install. What we need to do with this file is enter a directive that will give the server a name. Because we are not using a DNS server (as it is local) we need to let Apache know what to call itself. Enter the following directive.

ServerName localhost

Save this file and close it. When you are done you can restart the server by typing in the following command.

sudo apache2ctl -k restart

Your Apache server will now start with no annoying warnings or errors (as long as the rest of your configuration is correct).

Apache

Comments

apache is awesome, but  nginx is way more efficient.

Submitted by Anonymous coward on Wed, 09/21/2011 - 08:41

Permalink

Add new comment

The content of this field is kept private and will not be shown publicly.
CAPTCHA
2 + 1 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

Related Content

Speeding Up Apache And Drupal With Varnish

8th June 2014

Varnish is a web application accelerator that provides an easy speed increase to most web applications and Drupal is no exception. It works by creating a reverse proxy service that sits in front of your web server and caches traffic that comes through it.

Read more

Adding iptables Rules With Ansible

16th February 2014

Many systems and applications require certain access to certain ports and protocols. When installing these systems using Ansible it is necessary to also open up the needed ports so that the systems can function correctly. As there is no iptables module in Ansible the shell command is needed to add the iptables rules.

Read more

Turning Off Apache Basic Authentication For A Single Directory

11th September 2013

When setting up staging sites or similar I often add a simple Apache authentication check in order to stop everyone from viewing the site. This is also useful in stopping search engine spiders from accessing a site with testing content on it, which generally causes trouble. It isn't amazingly secure, but it keeps almost everyone out.

Read more

Using Phing To Create Apache Virtual Hosts

6th April 2012

Phing is an awesome tool for automating things and I use it more and more for automating all kinds of different tasks. One of the tasks that I don't tend to do all that much is setting up a new local virtual host for Apache on my development machines.

Read more

IE8 Downloading docx Files As zip On Apache

23rd January 2012

I recently built a Drupal site on an Apache server setup and everything seemed fine until someone running IE8 tried to download a .docx file. For some reason IE8 insisted that this file was a .zip file and would open it as such, causing a bit of confusion as to what the problem was.

Read more