This article covers a version of Ubuntu that is no longer supported. If you are currently operate a server running Ubuntu 12.04, we highly recommend upgrading or migrating to a supported version of Ubuntu:
Reason: Ubuntu 12.04 reached end of life (EOL) on April 28, 2017 and no longer receives security patches or updates. This guide is no longer maintained.
This guide might still be useful as a reference, but may not work on other Ubuntu releases. If available, we strongly recommend using a guide written for the version of Ubuntu you are using. You can use the search functionality at the top of the page to find a more recent version.
The lines that the user needs to enter or customize will be in red in this tutorial! The rest should mostly be copy-and-pastable.
Virtual Hosts are used to run more than one domain off of a single IP address. This is especially useful to people who need to run several sites off of one virtual private server. The sites display different information to the visitors, depending on with which the users accessed the site.There is no limit to the number of virtual hosts that can be added to a VPS.
The steps in this tutorial require the user to have root privileges. You can see how to set that up in the here Initial Server Setup. You can implement whatever username suits you.
Additionally, you need to have apache already installed and running on your virtual server If this is not the case, you can download it with this command:
sudo apt-get install apache2
The first step in creating a virtual host is to a create a directory where we will keep the new website’s information.
This location will be your Document Root in the Apache virtual configuration file later on. By adding a -p to the line of code, the command automatically generates all the parents for the new directory.
sudo mkdir -p /var/www/example.com/public_html
You will need to designate an actual DNS approved domain, or an IP address, to test that a virtual host is working. In this tutorial we will use example.com as a placeholder for a correct domain name.
However, should you want to use an unapproved domain name to test the process you will find information on how to make it work on your local computer in Step Seven.
We need to grant ownership of the directory to the user, instead of just keeping it on the root system.
sudo chown -R $USER:$USER /var/www/example.com/public_html
Additionally, it is important to make sure that everyone will be able to read our new files.
sudo chmod -R 755 /var/www
Now you are all done with permissions.
Within our configurations directory, we need to create a new file called index.html
sudo nano /var/www/example.com/public_html/index.html
We can add some text to the file so we will have something to look at when the IP redirects to the virtual host.
<html> <head> <title>www.example.com</title> </head> <body> <h1>Success: You Have Set Up a Virtual Host</h1> </body> </html>
Save and Exit
The next step is to set up the apache configuration. We’re going to work off a duplicate—go ahead and make a copy of the file (naming it after your domain name) in the same directory:
sudo cp /etc/apache2/sites-available/default /etc/apache2/sites-available/example.com
Open up the new config file:
sudo nano /etc/apache2/sites-available/example.com
We are going to set up a virtual host in this file.
The first step is to insert a line for the ServerName under the ServerAdmin line.
The ServerName specifies the domain name that the virtual host uses.
If you want to make your site accessible from more than one name (for example, with www in the URL), you can include the alternate names in your virtual host file by adding a ServerAlias Line. The beginning of your virtual host file would then look like this:
<VirtualHost *:80> ServerAdmin firstname.lastname@example.org ServerName example.com ServerAlias www.example.com [...]
The next step is to fill in the correct Document Root. For this section, write in the extension of the new directory created in Step One. If the document root is incorrect or absent you will not be able to set up the virtual host.
The section should look like this:
You do not need to make any other changes to this file. Save and Exit.
The last step is to activate the host, with the built in apache shortcut:
sudo a2ensite example.com
We’ve made a lot of the changes to the configuration, and the virtual host is set up. However none of the changes that we made will take effect until Apache is restarted.
Use this command to restart apache:
sudo service apache2 restart
You may see an error along the lines of
Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerNameThe message is just a warning, and you will be able to access your virtual host without any further issues.
If you have pointed your domain name to your virtual private server’s IP address you can skip this step—you do not need to set up local hosts. Your virtual hosts should work. However, if want to try out your new virtual hosts without having to connect to an actual domain name, you can set up local hosts on your computer alone. For this step, make sure you are on the computer itself, not your droplet.
To proceed with this step you need to know your computer’s administrative password, otherwise you will be required to use an actual domain name to test the virtual hosts.
If you are on a Mac or Linux, access the root user (
su) on the computer and open up your hosts file:
If you are on a Windows Computer, you can find the directions to alter the host file on the Microsoft site
You can add the local hosts details to this file, as seen in the example below. As long as that line is there, directing your browser toward, say, example.com will give you all the virtual host details for the corresponding IP address.
# Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost #Virtual Hosts 220.127.116.119 example.com
However, it may be a good idea to delete these made up addresses out of the local hosts folder when you are done to avoid any future confusion.
Once you have finished setting up your virtual host, you can see how it looks online. Type your ip address into the browser (ie. http://18.104.22.1689)
It should look somewhat similar to my handy screenshot
To add more virtual hosts, you can just repeat the process above, being careful to set up a new document root with the appropriate domain name, and then creating and activating the new virtual host file.
Once you have set up your virtual hosts, you can proceed to Create a SSL Certificate for your site or Install an FTP server
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Click below to sign up and get $200 of credit to try our products over 60 days!
How to call the url of virtual host ?
When I tried to activate the host (command: sudo a2ensite example.com), it told me ERROR: Site example.com does not exist!
I have a couple of small personal sites that are more landings than anything else. I’d like to use Apache on a droplet for this that I already have a 1-click Discourse install on. Will this create any problems or conflicts?
I have a trouble with a secondary instalation, I explain:
I have a one principal wordpress, and also have one more instalation wordpress. I followed all steps and my secondary domain works nice, Work ok the www.secondary.com and www.secondary.com/wp-admin (in other words, works the home page and the dashboard) BUT !!! doesnt work the pages, posts and others elements. Example:
www.secondary.com => Fine www.secondary.com/wp-admin => Fine
www.secondary.com/page1 => Dont Work www.secondary.com/post1 => Dont Work … www.secondary.com/element1 => Dont Work
I checked the .htaccess and its ok. So I think the trouble is with apache …
So … somebody help me with this … please is very important!
“ERROR: site example.com does not exit.”
Can Help me?
Has Step Four changed? i get ‘cp: cannot stat ‘/etc/apache2/sites-available/default’: No such file or directory’ when trying to copy the default file
It seems like when you copy the .conf file from sites-available to the same directory, you are not copying this file with the extension and then the comand a2ensite throws an error. Please can you edit this tutorial for another users dont have this problem? Thanks very much!!!
I followed all the instructions, when I type my global ip in the browser, it says problem loading page. What should I do? Also, my connection uses DHCP protocol.
One thing here, in apache2 under ubuntu, you need to put .conf at the end of the name of the config file, example: /etc/apache2/sites-available/example.com.conf
Otherwise a2ensite will not work.
I followed this exactly but when I navigate to the new address I just get this error:
503 Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.22 (Ubuntu) Server at <the site> Port 80