{"id":1,"date":"2025-05-01T20:24:59","date_gmt":"2025-05-01T20:24:59","guid":{"rendered":"http:\/\/www.khhtech.com\/?p=1"},"modified":"2025-05-23T13:01:25","modified_gmt":"2025-05-23T19:01:25","slug":"install-apache2-web-server-on-ubuntu-24-04","status":"publish","type":"post","link":"http:\/\/www.khhtech.com\/index.php\/2025\/05\/01\/install-apache2-web-server-on-ubuntu-24-04\/","title":{"rendered":"Install Apache 2.4 Web Server on Ubuntu 24.04 LTS Server"},"content":{"rendered":"\n

I needed a development Web Server on my in-house network for website development. This Web Server will not be visible to the outside Internet, only to computers logged on through the local network. These are the steps I used to install and configure the Apache 2.4 Web Server on a in-house Ubuntu 24.04 LTS server.<\/p>\n\n\n\n

Prerequisites:<\/strong><\/p>\n\n\n\n

Before installing any new applications, confirm that you system is up to date. Open your terminal window by pressing the Ctl, Alt and ‘T’ keys simultaneously. Enter the following command on the terminal.<\/p>\n\n\n\n

$ sudo apt update && sudo apt upgrade<\/code><\/pre>\n\n\n\n
Install mySQL and PHP before continuing with the Apache2 Web Server installation.<\/p>\n\n\n\n
Install Apache 2.4<\/strong>:<\/p>\n\n\n\n
To install the Apache2 Web Server, enter the following command.<\/p>\n\n\n\n
$ sudo apt install apache2<\/code><\/pre>\n\n\n\n
Start the service and confirm the installation.<\/p>\n\n\n\n
$ sudo systemctl start apache2\n$ sudo systemctl status apache2<\/code><\/pre>\n\n\n\n
The status command will display the following results, indicating the the Apache2 service is running.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Another way to test that the Apache2 Web Server is active is by viewing the default Apache2 web page. Open a browser on the Ubuntu Server, where Apache2 is installed, and type http:\/\/localhost\/<\/strong> in the browser’s address line. This page will display on the browser showing that Apache2 is working correctly.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Open Listening Ports:<\/strong><\/p>\n\n\n\n
If you have an active firewall on Ubuntu Server you will need to open the necessary ports for communication. Apache, by default, listens on port 80 (HTTP) and port 443 (HTTPS). The command below will open these ports on the Ubuntu Server. If you have configured Apache2 to use ports other than 80 and 443, you will need to adjust this command to open the correct ports.<\/p>\n\n\n\n
$ sudo ufw allow 'Apache Full'<\/code><\/pre>\n\n\n\n
You can confirm the change with this commend.<\/p>\n\n\n\n
$ sudo ufw status<\/code><\/pre>\n\n\n\n
The output will show that HTTP and HTTPS traffic is allowed.<\/p>\n\n\n\n
Status: active\n\nTo                         Action      From\n--                         ------      ----\nApache Full                ALLOW       Anywhere\nOpenSSH                    ALLOW       Anywhere\nApache Full (v6)           Allow       Anywhere (v6)\nOpenSSH (v6)               ALLOW       Anywhere (v6)<\/code><\/pre>\n\n\n\n
Create Website Directory:<\/strong><\/p>\n\n\n\n
Now create a directory for the development website files and folders. By default Apache2’s web root is located in \/var\/www\/html. But a new website directory can be located anywhere. For this development website I created it at \/var\/www\/ and called it example.com using the following command.<\/p>\n\n\n\n
$ sudo mkdir \/var\/www\/example.com<\/code><\/pre>\n\n\n\n
Then below the example.com directory I create a \/public_html\/ directory. This is where all the website files and folders will be created.<\/p>\n\n\n\n
$ sudo mkdir \/var\/www\/example.com\/public_html<\/code><\/pre>\n\n\n\n
Set Directory Permissions:<\/strong><\/p>\n\n\n\n
Set ownership of the directory to your Ubuntu username, to avoid permission issues, when creating files.<\/p>\n\n\n\n
$ sudo chown -R $USER:$USER \/var\/www\/example.com\/public_html\n$ sudo chmod -R 755 \/var\/www\/example.com\/public_html<\/code><\/pre>\n\n\n\n
Configure Virtual Host:<\/strong><\/p>\n\n\n\n
To allow the Apache2 Web Server to serve this web app, using a domain name of your choice, you will add it to a virtual host file in the \/etc\/apache2\/sites-available\/ directory. There is already a virtual host file, named 000-default.conf, located in this folder. This is the virtual host file that Apache2 is using to server the default web page. You can use the 000-default.conf file for your new web app. But it is best to create an new file, with a name that has a meaning for you, for the new virtual host. In my case I decided on using the file name vhosts.conf<\/strong>. Change directories to the \/etc\/apache2\/sites-available\/ directory. Using the VI text editor, I created a vhosts.conf file.<\/p>\n\n\n\n
$ cd \/etc\/apache2\/sites-available\n$ sudo vi vhosts.conf<\/code><\/pre>\n\n\n\n
Within this file I entered and saved the following block.<\/p>\n\n\n\n
<VirtualHost *:80>\n    ServerAdmin webmaster@example.com\n    ServerName example.com\n    ServerAlias www.example.com\n    DocumentRoot \/var\/www\/example.com\/public_html\n    ErrorLog ${APACHE_LOG_DIR}\/error.log\n    CustomLog ${APACHE_LOG_DIR}\/access.log combined\n<\/VirtualHost><\/code><\/pre>\n\n\n\n
Enable the vhosts.conf file with the a2ensite<\/strong> tool.<\/p>\n\n\n\n
$ sudo a2ensite vhosts.conf<\/code><\/pre>\n\n\n\n
But before Apache2 will serve this new web app, you will need to disable the 000-default.conf file. Do this with the a2dissite<\/strong> tool.<\/p>\n\n\n\n
$ sudo a2dissite 000-default.conf<\/code><\/pre>\n\n\n\n
Then, test for configuration errors in the virtual host file.<\/p>\n\n\n\n
$ sudo apache2ctl configtest<\/code><\/pre>\n\n\n\n
The following output will indicate no errors in the virtual host file.<\/p>\n\n\n\n
Output\nSyntax OK<\/code><\/pre>\n\n\n\n
Restart Apache2 to apply the changes.<\/p>\n\n\n\n
$ sudo systemctl restart apache2<\/code><\/pre>\n\n\n\n
Create a Test Web Page:<\/strong><\/p>\n\n\n\n
Create a simple index.html<\/strong> page for the example.com web app. Using a text editor open a file in the \/var\/www\/example.com\/public_html directory<\/p>\n\n\n\n
$ sudo vi \/var\/www\/example.com\/public_html\/index.html<\/code><\/pre>\n\n\n\n
Add the following html code to the index.html file and save the file.<\/p>\n\n\n\n
<!DOCTYPE html>\n<html>\n<head>\n   <title>Test example.com Web Page<\/title>\n<\/head>\n<body>\n   <h1>Welcome the the EXAMPLE.COM Web Page!<\/h1>\n<\/body>\n<\/html><\/code><\/pre>\n\n\n\n
Modify the Hosts file to resolve domain:<\/strong><\/p>\n\n\n\n
Modifying the DNS Server is the preferred way to resolve domain names. But for small development environments, the Hosts files on the Ubuntu Server, and each computer needing to access the domain, can be modified. To configure the Ubuntu Server’s Hosts file, open the Hosts file with a text editor – such a notepad – enter the URL you will use for the web site on the same line as the localhost, each seperated by a space.<\/p>\n\n\n\n
The Ubuntu Server’s Hosts file will look like this.<\/p>\n\n\n\n
127.0.0.1          localhost example.com www.example.com<\/strong><\/mark>\n127.0.1.1          ubuntu-server-name<\/code><\/pre>\n\n\n\n
To configure the individual’s computer Hosts file, open its Hosts file and, on a new line, enter the Ubuntu Server’s IP Address, followed by the URL you will use for the web site. Below is an example of what the Hosts file may like with the website URL added.<\/p>\n\n\n\n
127.0.0.1          localhost\n127.0.1.1          ubuntu-server-name \n192.168.1.2        www.example.com<\/mark><\/strong> example.com<\/strong><\/mark><\/code><\/pre>\n\n\n\n
Apache2 should now be serving the example.com domain name. Test it by opening a browser and entering the URL http:\/\/www.example.com in the address line.<\/p>\n","protected":false},"excerpt":{"rendered":"
Install Apache 2.4.Web Server on Ubuntu 24.04 LTS Server<\/p>\n
I needed a development Web Server on my in-house network for website development. This Web Server will not visible to the outside Internet, only to computers logged on to the local network. These are the steps I used to install and configure the Apache 2.4 Web Server on a in-house Ubuntu 24.04 LTS server.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,7],"tags":[],"class_list":["post-1","post","type-post","status-publish","format-standard","hentry","category-apache2","category-ubuntu"],"_links":{"self":[{"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/posts\/1","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/comments?post=1"}],"version-history":[{"count":48,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/posts\/1\/revisions"}],"predecessor-version":[{"id":260,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/posts\/1\/revisions\/260"}],"wp:attachment":[{"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/media?parent=1"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/categories?post=1"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.khhtech.com\/index.php\/wp-json\/wp\/v2\/tags?post=1"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}