{"id":382,"date":"2019-06-03T15:57:23","date_gmt":"2019-06-03T15:57:23","guid":{"rendered":"https:\/\/blog.iabsolute.com\/?p=382"},"modified":"2019-06-03T15:58:16","modified_gmt":"2019-06-03T22:58:16","slug":"how-to-install-the-apache-web-server-on-centos-7","status":"publish","type":"post","link":"https:\/\/blog.iabsolute.com\/?p=382","title":{"rendered":"How To Install the Apache Web Server on CentOS 7"},"content":{"rendered":"\n

Step 1 \u2014 Installing Apache<\/h2>\n\n\n\n

Apache is available within CentOS’s default software repositories, which means you can install it with the yum<\/code> package manager.<\/p>\n\n\n\n

As the non-root sudo user configured in the prerequisites, update the local Apache httpd<\/code> package index to reflect the latest upstream changes:<\/p>\n\n\n\n

sudo yum update httpd\n<\/code><\/pre>\n\n\n\n
Once the packages are updated, install the Apache package:<\/p>\n\n\n\n
sudo yum install httpd\n<\/code><\/pre>\n\n\n\n
After confirming the installation, yum<\/code> will install Apache and all required dependencies. Once the installation completes, you are ready to start the service. <\/p>\n\n\n\n
Step 2 \u2014 Checking your Web Server<\/h2>\n\n\n\n
Apache does not automatically start on CentOS once the installation completes. You will need to start the Apache process manually:<\/p>\n\n\n\n
sudo systemctl start httpd\n<\/code><\/pre>\n\n\n\n
Verify that the service is running with the following command:<\/p>\n\n\n\n
sudo systemctl status httpd\n<\/code><\/pre>\n\n\n\n
You will see an active<\/code> status when the service is running:<\/p>\n\n\n\n
OutputRedirecting to \/bin\/systemctl status httpd.service\n\u25cf httpd.service - The Apache HTTP Server\n   Loaded: loaded (\/usr\/lib\/systemd\/system\/httpd.service; enabled; vendor preset: disabled)\n   Active: active (running) since Wed 2019-02-20 01:29:08 UTC; 5s ago\n     Docs: man:httpd(8)\n           man:apachectl(8)\n Main PID: 1290 (httpd)\n   Status: \"Processing requests...\"\n   CGroup: \/system.slice\/httpd.service\n           \u251c\u25001290 \/usr\/sbin\/httpd -DFOREGROUND\n           \u251c\u25001291 \/usr\/sbin\/httpd -DFOREGROUND\n           \u251c\u25001292 \/usr\/sbin\/httpd -DFOREGROUND\n           \u251c\u25001293 \/usr\/sbin\/httpd -DFOREGROUND\n           \u251c\u25001294 \/usr\/sbin\/httpd -DFOREGROUND\n           \u2514\u25001295 \/usr\/sbin\/httpd -DFOREGROUND\n...\n<\/code><\/pre>\n\n\n\n
As you can see from this output, the service appears to have started successfully. However, the best way to test this is to request a page from Apache.<\/p>\n\n\n\n
You can access the default Apache landing page to confirm that the software is running properly through your IP address. If you do not know your server’s IP address, you can get it a few different ways from the command line.<\/p>\n\n\n\n
Type this at your server’s command prompt:<\/p>\n\n\n\n
hostname -I\n<\/code><\/pre>\n\n\n\n
This command will display all of the host’s network addresses, so you will get back a few IP addresses separated by spaces. You can try each in your web browser to see if they work.<\/p>\n\n\n\n
Alternatively, you can use curl<\/code> to request your IP from icanhazip.com<\/code>, which will give you your public IPv4 address as seen from another location on the internet:<\/p>\n\n\n\n
curl -4 icanhazip.com\n<\/code><\/pre>\n\n\n\n
When you have your server’s IP address, enter it into your browser’s address bar:<\/p>\n\n\n\n
http:\/\/your_server_ip\n<\/code><\/pre>\n\n\n\n
You’ll see the default CentOS 7 Apache web page:<\/p>\n\n\n\n
This page indicates that Apache is working correctly. It also includes some basic information about important Apache files and directory locations. Now that the service is installed and running, you can now use different systemctl<\/code> commands to manage the service.<\/p>\n\n\n\n
Step 3 \u2014 Managing the Apache Process<\/h2>\n\n\n\n
Now that you have your web server up and running, let’s go over some basic management commands.<\/p>\n\n\n\n
To stop your web server, type:<\/p>\n\n\n\n
sudo systemctl stop httpd\n<\/code><\/pre>\n\n\n\n
To start the web server when it is stopped, type:<\/p>\n\n\n\n
sudo systemctl start httpd\n<\/code><\/pre>\n\n\n\n
To stop and then start the service again, type:<\/p>\n\n\n\n
sudo systemctl restart httpd\n<\/code><\/pre>\n\n\n\n
If you are simply making configuration changes, Apache can often reload without dropping connections. To do this, use this command:<\/p>\n\n\n\n
sudo systemctl reload httpd\n<\/code><\/pre>\n\n\n\n
By default, Apache is configured to start automatically when the server boots. If this is not what you want, disable this behavior by typing:<\/p>\n\n\n\n
sudo systemctl disable httpd\n<\/code><\/pre>\n\n\n\n
To re-enable the service to start up at boot, type:<\/p>\n\n\n\n
sudo systemctl enable httpd\n<\/code><\/pre>\n\n\n\n
Apache will now start automatically when the server boots again. <\/p>\n\n\n\n
The default configuration for Apache will allow your server to host a single website. If you plan on hosting multiple domains on your server, you will need to configure virtual hosts on your Apache web server.<\/p>\n\n\n\n
Step 4 \u2014 Setting Up Virtual Hosts (Recommended)<\/h2>\n\n\n\n
When using the Apache web server, you can use virtual hosts<\/em> (similar to server blocks in Nginx) to encapsulate configuration details and host more than one domain from a single server. In this step, you will set up a domain called example.com<\/code>, but you should replace this with your own domain name. To learn more about setting up a domain name with DigitalOcean, see our Introduction to DigitalOcean DNS<\/a>.<\/p>\n\n\n\n
Apache on CentOS 7 has one server block enabled by default that is configured to serve documents from the \/var\/www\/html<\/code> directory. While this works well for a single site, it can become unwieldy if you are hosting multiple sites. Instead of modifying \/var\/www\/html<\/code>, you will create a directory structure within \/var\/www<\/code> for the example.com<\/code> site, leaving \/var\/www\/html<\/code> in place as the default directory to be served if a client request doesn’t match any other sites.<\/p>\n\n\n\n
Create the html<\/code> directory for example.com<\/code> as follows, using the -p<\/code> flag to create any necessary parent directories:<\/p>\n\n\n\n
sudo mkdir -p \/var\/www\/example.com\/html\n<\/code><\/pre>\n\n\n\n
Create an additional directory to store log files for the site:<\/p>\n\n\n\n
sudo mkdir -p \/var\/www\/example.com\/log\n<\/code><\/pre>\n\n\n\n
Next, assign ownership of the html<\/code> directory with the $USER<\/code> environmental variable:<\/p>\n\n\n\n
sudo chown -R $USER:$USER \/var\/www\/example.com\/html\n<\/code><\/pre>\n\n\n\n
Make sure that your web root has the default permissions set:<\/p>\n\n\n\n
sudo chmod -R 755 \/var\/www\n<\/code><\/pre>\n\n\n\n
Next, create a sample index.html<\/code> page using vi<\/code> or your favorite editor:<\/p>\n\n\n\n
sudo vi \/var\/www\/example.com\/html\/index.html\n<\/code><\/pre>\n\n\n\n
Press i<\/code> to switch to INSERT<\/code> mode and add the following sample HTML to the file:\/var\/www\/example.com\/html\/index.html<\/p>\n\n\n\n
<html>\n  <head>\n    <title>Welcome to Example.com!<\/title>\n  <\/head>\n  <body>\n    <h1>Success! The example.com virtual host is working!<\/h1>\n  <\/body>\n<\/html>\n<\/code><\/pre>\n\n\n\n
Save and close the file by pressing ESC<\/code>, typing :wq<\/code>, and pressing ENTER<\/code>. <\/p>\n\n\n\n
With your site directory and sample index file in place, you are almost ready to create the virtual host files. Virtual host files specify the configuration of your separate sites and tell the Apache web server how to respond to various domain requests.<\/p>\n\n\n\n
Before you create your virtual hosts, you will need to create a sites-available<\/code> directory to store them in. You will also create the sites-enabled<\/code> directory that tells Apache that a virtual host is ready to serve to visitors. The sites-enabled<\/code> directory will hold symbolic links to virtual hosts that we want to publish. Create both directories with the following command:<\/p>\n\n\n\n
sudo mkdir \/etc\/httpd\/sites-available \/etc\/httpd\/sites-enabled\n<\/code><\/pre>\n\n\n\n
Next, you will tell Apache to look for virtual hosts in the sites-enabled<\/code> directory. To accomplish this, edit Apache’s main configuration file and add a line declaring an optional directory for additional configuration files:<\/p>\n\n\n\n
sudo vi \/etc\/httpd\/conf\/httpd.conf\n<\/code><\/pre>\n\n\n\n
Add this line to the end of the file:<\/p>\n\n\n\n
IncludeOptional sites-enabled\/*.conf\n<\/code><\/pre>\n\n\n\n
Save and close the file when you are done adding that line. Now that you have your virtual host directories in place, you will create your virtual host file.<\/p>\n\n\n\n
Start by creating a new file in the sites-available<\/code> directory:<\/p>\n\n\n\n
sudo vi \/etc\/httpd\/sites-available\/example.com.conf\n<\/code><\/pre>\n\n\n\n
Add in the following configuration block, and change the example.com<\/code> domain to your domain name: \/etc\/httpd\/sites-available\/example.com.conf<\/p>\n\n\n\n
<VirtualHost *:80>\n    ServerName www.example.com\n    ServerAlias example.com\n    DocumentRoot \/var\/www\/example.com\/html\n    ErrorLog \/var\/www\/example.com\/log\/error.log\n    CustomLog \/var\/www\/example.com\/log\/requests.log combined\n<\/VirtualHost>\n<\/code><\/pre>\n\n\n\n
This will tell Apache where to find the root directly that holds the publicly accessible web documents. It also tells Apache where to store error and request logs for this particular site.<\/p>\n\n\n\n
Save and close the file when you are finished.<\/p>\n\n\n\n
Now that you have created the virtual host files, you will enable them so that Apache knows to serve them to visitors. To do this, create a symbolic link for each virtual host in the sites-enabled<\/code> directory:<\/p>\n\n\n\n
sudo ln -s \/etc\/httpd\/sites-available\/example.com.conf \/etc\/httpd\/sites-enabled\/example.com.conf\n<\/code><\/pre>\n\n\n\n
Your virtual host is now configured and ready to serve content. Before restarting the Apache service, let’s make sure that SELinux has the correct policies in place for your virtual hosts.<\/p>\n\n\n\n
Step 5 \u2014 Adjusting SELinux Permissions for Virtual Hosts (Recommended)<\/h2>\n\n\n\n
SELinux<\/a> is configured to work with the default Apache configuration. Since you set up a custom log directory in the virtual hosts configuration file, you will receive an error if you attempt to start the Apache service. To resolve this, you need to update the SELinux policies to allow Apache to write to the necessary files. SELinux brings heightened security to your CentOS 7 environment, therefore it is not recommended to completely disable the kernel module. <\/p>\n\n\n\n
There are different ways to set policies based on your environment’s needs, as SELinux allows you to customize your security level. This step will cover two methods of adjusting Apache policies: universally and on a specific directory. Adjusting policies on directories is more secure, and is therefore the recommended approach.<\/p>\n\n\n\n
Adjusting Apache Policies Universally<\/h3>\n\n\n\n
Setting the Apache policy universally will tell SELinux to treat all Apache processes identically by using the httpd_unified<\/code> boolean. While this approach is more convenient, it will not give you the same level of control as an approach that focuses on a file or directory policy.<\/p>\n\n\n\n
Run the following command to set a universal Apache policy:<\/p>\n\n\n\n
sudo setsebool -P httpd_unified 1\n<\/code><\/pre>\n\n\n\n
The setsebool<\/code> command changes SELinux boolean values. The -P<\/code> flag will update the boot-time value, making this change persist across reboots. httpd_unified<\/code> is the boolean that will tell SELinux to treat all Apache processes as the same type, so you enabled it with a value of 1<\/code>. <\/p>\n\n\n\n
Adjusting Apache Policies on a Directory<\/h3>\n\n\n\n
Individually setting SELinux permissions for the \/var\/www\/example.com\/log<\/code> directory will give you more control over your Apache policies, but may also require more maintenance. Since this option is not universally setting policies, you will need to manually set the context type for any new log directories specified in your virtual host configurations.<\/p>\n\n\n\n
First, check the context type that SELinux gave the \/var\/www\/example.com\/log<\/code> directory:<\/p>\n\n\n\n
sudo ls -dZ \/var\/www\/example.com\/log\/\n<\/code><\/pre>\n\n\n\n
This command lists and prints the SELinux context of the directory. You will see output similar to the following:<\/p>\n\n\n\n
Outputdrwxr-xr-x. root root unconfined_u:object_r:httpd_sys_content_t:s0 \/var\/www\/example.com\/log\/\n<\/code><\/pre>\n\n\n\n
The current context is httpd_sys_content_t<\/code>, which tells SELinux that the Apache process can only read files created in this directory. In this tutorial, you will change the context type of the \/var\/www\/example.com\/log<\/code> directory to httpd_log_t<\/code>. This type will allow Apache to generate and append to web application log files:<\/p>\n\n\n\n
sudo semanage fcontext -a -t httpd_log_t \"\/var\/www\/example.com\/log(\/.*)?\"\n<\/code><\/pre>\n\n\n\n
Next, use the restorecon<\/code> command to apply these changes and have them persist across reboots:<\/p>\n\n\n\n
sudo restorecon -R -v \/var\/www\/example.com\/log\n<\/code><\/pre>\n\n\n\n
The -R<\/code> flag runs this command recursively, meaning it will update any existing files to use the new context. The -v<\/code> flag will print the context changes the command made. You will see the following output confirming the changes:<\/p>\n\n\n\n
Outputrestorecon reset \/var\/www\/example.com\/log context unconfined_u:object_r:httpd_sys_content_t:s0->unconfined_u:object_r:httpd_log_t:s0\n<\/code><\/pre>\n\n\n\n
You can list the contexts once more to see the changes:<\/p>\n\n\n\n
sudo ls -dZ \/var\/www\/example.com\/log\/\n<\/code><\/pre>\n\n\n\n
The output reflects the updated context type:<\/p>\n\n\n\n
Outputdrwxr-xr-x. root root unconfined_u:object_r:httpd_log_t:s0 \/var\/www\/example.com\/log\n<\/code><\/pre>\n\n\n\n
Now that the \/var\/www\/example.com\/log<\/code> directory is using the httpd_log_t<\/code> type, you are ready to test your virtual host configuration.<\/p>\n\n\n\n
Step 6 \u2014 Testing the Virtual Host (Recommended)<\/h2>\n\n\n\n
Once the SELinux context has been updated with either method, Apache will be able to write to the \/var\/www\/example.com\/log<\/code> directory. You can now successfully restart the Apache service:<\/p>\n\n\n\n
sudo systemctl restart httpd\n<\/code><\/pre>\n\n\n\n
List the contents of the \/var\/www\/example.com\/log<\/code> directory to see if Apache created the log files:<\/p>\n\n\n\n
ls -lZ \/var\/www\/example.com\/log\n<\/code><\/pre>\n\n\n\n
You’ll see that Apache was able to create the error.log<\/code> and requests.log<\/code> files specified in the virtual host configuration:<\/p>\n\n\n\n
Output-rw-r--r--. 1 root root 0 Feb 26 22:54 error.log\n-rw-r--r--. 1 root root 0 Feb 26 22:54 requests.log\n<\/code><\/pre>\n\n\n\n
Now that you have your virtual host set up and SELinux permissions updated, Apache will now serve your domain name. You can test this by navigating to http:\/\/example.com<\/code>, where you should see something like this:<\/p>\n\n\n\n
\"Success!<\/figure>\n","protected":false},"excerpt":{"rendered":"
Step 1 \u2014 Installing Apache Apache is available within CentOS’s default software repositories, which means you can install it with the yum package manager. As the non-root sudo user configured in the prerequisites, update the local Apache httpd package index … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25,10],"tags":[],"class_list":["post-382","post","type-post","status-publish","format-standard","hentry","category-apache","category-centos"],"_links":{"self":[{"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/posts\/382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=382"}],"version-history":[{"count":2,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/posts\/382\/revisions"}],"predecessor-version":[{"id":384,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=\/wp\/v2\/posts\/382\/revisions\/384"}],"wp:attachment":[{"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.iabsolute.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}