View All Products
Compute
Storage
Databases
Networking
Developer Tools
Delivery
Security
Services
Industries
Pricing
Community
Engage With Us

Installing Apache Web Server on CentOS 8

Published by Linode
Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

The Apache HTTP Web Server (Apache) is an open source web application for deploying web servers. This guide explains how to install and configure an Apache web server on CentOS 8.

If instead you would like to install a full LAMP (Linux, Apache, MySQL and PHP) stack, please see the How to Install a LAMP Stack on CentOS 8 guide.

Before You Begin

  1. Set up your Linode in the Creating a Compute Instance and Setting Up and Securing a Compute Instance guide.

  2. If you want a custom domain name for your site, you can set this up using our DNS Manager guide.

  3. Install the SELinux core policy Python utilities. This will give you the ability to manage SELinux settings in a fine-grained way.

     sudo yum install -y policycoreutils-python-utils
    Note

    This guide is written for a non-root user. Commands that require elevated privileges are prefixed with sudo. If you’re not familiar with the sudo command, visit our Users and Groups guide.

    All configuration files should be edited with elevated privileges. Remember to include sudo before running your text editor.

Install Apache

  1. Install Apache 2.4:

    sudo yum install httpd

  2. Enable and start the Apache service:

    sudo systemctl enable httpd.service
sudo systemctl start httpd.service

  3. Open the firewall for both http and https:

    sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https

  4. Reload the firewall:

    sudo firewall-cmd --reload

Multi-Processing Modules

Apache 2.4 offers several multi-processing modules (MPMs) to handle connections. In CentOS 8 the default MPM is the event module, although the prefork module is still recommended if you’re using standard PHP. Below are the basic default settings. For detailed explanations and advanced settings for these modules, see the Tuning Your Apache Server guide.

  1. You can check which MPM is currently configured with the following command:

    sudo httpd -V | grep -i mpm

    Server MPM:     event

  2. Before making changes to your configuration file, make a backup:

    sudo cp /etc/httpd/conf/httpd.conf ~/httpd.conf.backup

The Prefork Module

The Prefork Module is ideal for single threaded applications. It’s a single parent with multiple forked child servers that are identical processes which wait for incoming requests. Each child process handles a single request. The Prefork Module is resource intensive but necessary for applications that do not support multi-threading such as PHP.

  1. Add the following section to the /etc/httpd/conf/httpd.conf file in your text editor and edit the values as needed. The following are the default values:

    File: /etc/httpd/conf/httpd.conf
    1
2
3
4
5
6
7

    <IfModule prefork.c>
        StartServers              5
        MinSpareServers           5
        MaxSpareServers           10
        MaxRequestWorkers         150
        MaxConnectionsPerChild    0
</IfModule>

  2. On CentOS 8, the event module is enabled by default. Disable it, and enable the prefork module edit the /etc/httpd/conf.modules.d/00-mpm.conf file. Comment out the line for the event module and uncomment the line for the prefork module:

    File: /etc/httpd/conf.modules.d/00-mpm.conf
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

    # Select the MPM module which should be used by uncommenting exactly
# one of the following LoadModule lines.  See the httpd.conf(5) man
# page for more information on changing the MPM.

# prefork MPM: Implements a non-threaded, pre-forking web server
# See: http://httpd.apache.org/docs/2.4/mod/prefork.html
#
# NOTE: If enabling prefork, the httpd_graceful_shutdown SELinux
# boolean should be enabled, to allow graceful stop/shutdown.
#
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so

# worker MPM: Multi-Processing Module implementing a hybrid
# multi-threaded multi-process web server
# See: http://httpd.apache.org/docs/2.4/mod/worker.html
#
#LoadModule mpm_worker_module modules/mod_mpm_worker.so

# event MPM: A variant of the worker MPM with the goal of consuming
# threads only for connections with active processing
# See: http://httpd.apache.org/docs/2.4/mod/event.html
#
#LoadModule mpm_event_module modules/mod_mpm_event.so

  3. Restart Apache:

    sudo systemctl restart httpd

The Worker Module

The Worker Module is a hybrid Prefork, multi-threaded, multi-processor module. It’s similar to the Prefork Module, but each child is multi-threaded.

  1. Add the following section to the /etc/httpd/conf/httpd.conf file in your text editor and edit the values as needed. The following are the default values:

    File: /etc/httpd/conf/httpd.conf
    <IfModule worker.c>
        StartServers             2
        MinSpareThreads          25
        MaxSpareThreads          75
        ThreadLimit              64
        ThreadsPerChild          25
        MaxRequestWorkers        150
        MaxConnectionsPerChild   0
</IfModule>

  2. On CentOS 8, the event module is enabled by default. Disable it, and enable the worker module edit the /etc/httpd/conf.modules.d/00-mpm.conf file. Comment out the line for the event module and uncomment the line for the worker module:

    File: /etc/httpd/conf.modules.d/00-mpm.conf
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

    # Select the MPM module which should be used by uncommenting exactly
# one of the following LoadModule lines.  See the httpd.conf(5) man
# page for more information on changing the MPM.

# prefork MPM: Implements a non-threaded, pre-forking web server
# See: http://httpd.apache.org/docs/2.4/mod/prefork.html
#
# NOTE: If enabling prefork, the httpd_graceful_shutdown SELinux
# boolean should be enabled, to allow graceful stop/shutdown.
#
#LoadModule mpm_prefork_module modules/mod_mpm_prefork.so

# worker MPM: Multi-Processing Module implementing a hybrid
# multi-threaded multi-process web server
# See: http://httpd.apache.org/docs/2.4/mod/worker.html
#
LoadModule mpm_worker_module modules/mod_mpm_worker.so

# event MPM: A variant of the worker MPM with the goal of consuming
# threads only for connections with active processing
# See: http://httpd.apache.org/docs/2.4/mod/event.html
#
#LoadModule mpm_event_module modules/mod_mpm_event.so

  3. Restart Apache:

    sudo systemctl restart httpd

The Event Module

The Event Module is similar to the Worker Module except each thread has a dedicated listener so that threads are not locked in wait. As of Apache 2.4 the Event Module is considered stable, for versions before 2.4, use the Worker Module.

  1. If you choose to keep the event module enabled, open /etc/httpd/conf/httpd.conf in your text editor, add this section to the end, and edit the values as needed. The following are the default values:

    File: /etc/httpd/conf/httpd.conf
    1
2
3
4
5
6
7
8
9

    <IfModule event.c>
        StartServers             2
        MinSpareThreads          25
        MaxSpareThreads          75
        ThreadLimit              64
        ThreadsPerChild          25
        MaxRequestWorkers        150
        MaxConnectionsPerChild   0
</IfModule>

  2. Be sure the event module is enabled. Edit the /etc/httpd/conf.modules.d/00-mpm.conf file. Comment out the lines for the prefork and worker modules and uncomment the line for the event module:

    File: /etc/httpd/conf.modules.d/00-mpm.conf
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

    # Select the MPM module which should be used by uncommenting exactly
# one of the following LoadModule lines.  See the httpd.conf(5) man
# page for more information on changing the MPM.

# prefork MPM: Implements a non-threaded, pre-forking web server
# See: http://httpd.apache.org/docs/2.4/mod/prefork.html
#
# NOTE: If enabling prefork, the httpd_graceful_shutdown SELinux
# boolean should be enabled, to allow graceful stop/shutdown.
#
#LoadModule mpm_prefork_module modules/mod_mpm_prefork.so

# worker MPM: Multi-Processing Module implementing a hybrid
# multi-threaded multi-process web server
# See: http://httpd.apache.org/docs/2.4/mod/worker.html
#
#LoadModule mpm_worker_module modules/mod_mpm_worker.so

# event MPM: A variant of the worker MPM with the goal of consuming
# threads only for connections with active processing
# See: http://httpd.apache.org/docs/2.4/mod/event.html
#
LoadModule mpm_event_module modules/mod_mpm_event.so

  3. Restart Apache:

    sudo systemctl restart httpd

Configure Virtual Hosting

Apache supports name-based virtual hosting, which allows you to host multiple domains on a single server with a single IP. Although there are different ways to set up virtual hosts, the method below is recommended.

  1. Create the directories for the virtual hosts:

    sudo mkdir /etc/httpd/sites-available
sudo mkdir /etc/httpd/sites-enabled

  2. Edit the /etc/httpd/conf/httpd.conf configuration file to tell Apache to look at these new directories for virtual hosts. Add the following line:

    File: /etc/httpd/conf/httpd.conf
    1

    IncludeOptional sites-enabled/*.conf

  3. Create an example.com.conf file in /etc/httpd/sites-available with your text editor, replacing instances of example.com with your own domain URL in both the configuration file and in the file name:

    File: /etc/httpd/sites-available/example.com.conf
    1
2
3
4
5
6
7
8

    <VirtualHost *:80>
     ServerAdmin webmaster@example.com
     ServerName example.com
     ServerAlias www.example.com
     DocumentRoot /var/www/example.com/public_html/
     ErrorLog /var/www/example.com/logs/error.log
     CustomLog /var/www/example.com/logs/access.log combined
</VirtualHost>

    Repeat this process for any other domains you host.

  4. Create a symbolic link to the sites-enabled directory for each virtual host:

    sudo ln -s /etc/httpd/sites-available/example.com.conf /etc/httpd/sites-enabled/example.com.conf

  5. Create directories for your websites and websites’ logs, replacing example.com with your own domain information:

    sudo mkdir -p /var/www/example.com/public_html
sudo mkdir /var/www/example.com/logs

  6. Change the ownership of the public_html directory to yourself:

    sudo chown -R $USER:$USER /var/www/example.com/public_html

  7. Change the permissions on the /var/www directory:

    sudo chmod -R 755 /var/www

  8. Create a simple page for your index.html.

    File: /var/www/example.com/public_html/index.html
    1
2
3
4
5
6
7
8
9

    <!DOCTYPE html>
<html>
    <head>
        <title>Hello World</title>
    </head>
    <body>
        <h1>Hello World! This is my sample website with Apache on CentOS!</h1>
    </body>
</html>

  9. Configure SELinux policies on the log directory for each virtual host. This will allow Apache to create and write to the log files. The restorecon command applies this setting and persists after a reboot:

    sudo semanage fcontext -a -t httpd_log_t "/var/www/example.com/logs(/.*)?"
sudo restorecon -R -v /var/www/example.com/logs

  10. You’ll see the following output:

    Relabeled /var/www/example.com/logs from unconfined_u:object_r:httpd_sys_content_t:s0 to unconfined_u:object_r:httpd_log_t:s0

  11. Use can further confirm setting was successful by using the following command:

    sudo ls -dZ /var/www/example.com/logs/

    unconfined_u:object_r:httpd_log_t:s0 /var/www/example.com/logs

    You should see httpd_log_t in this line.

  12. Restart Apache:

    sudo systemctl restart httpd

  13. Visit your site by navigating to your domain name in the web browser.

Apache Mods and Scripting

Install Apache Modules

One of Apache’s strengths is its ability to be customized with modules. The default installation directory for Apache modules is the /etc/httpd/modules/ directory. Configuration directives for the default modules are located in /etc/httpd/conf/httpd.conf, while configuration options for optional modules installed with yum are generally placed in .conf files in /etc/httpd/conf.d/.

  1. List available Apache modules:

    sudo yum search mod_

  2. Install any desired modules:

    sudo yum install [module-name]

    Modules should be enabled and ready to use following installation.

Optional: Install Support for Scripting

The following commands install Apache support for server-side scripting in Perl, Python, and PHP. Support for these languages is optional based on your server environment.

Install the EPEL repository:

sudo yum install epel-release

To install:

  • Perl support:

    sudo yum install mod_perl

  • Python support:

    sudo yum install mod_wsgi

  • PHP support:

    sudo yum install php php-pear

Check Server Status

You can check your Apache web server status with the following command:

sudo systemctl status httpd

The output will look similar to the following:

● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disab>
   Active: active (running) since Tue 2020-03-03 08:32:02 EST; 10s ago
     Docs: man:httpd.service(8)
 Main PID: 4251 (httpd)
   Status: "Running, listening on: port 80"
    Tasks: 213 (limit: 5083)
   Memory: 24.2M
   CGroup: /system.slice/httpd.service
           ├─4251 /usr/sbin/httpd -DFOREGROUND
           ├─4252 /usr/sbin/httpd -DFOREGROUND
           ├─4253 /usr/sbin/httpd -DFOREGROUND
           ├─4254 /usr/sbin/httpd -DFOREGROUND
           └─4255 /usr/sbin/httpd -DFOREGROUND

  • From here you can see that the server is running successfully. However, if something isn’t working correctly, you can check the logs for errors. The logs locations are defined for each virtual host you set up in Configure Virtual Hosting.

  • Typically they will be at /var/www/example.com/logs/error.log and /var/www/example.com/logs/access.log where example.com is your domain name.

Controlling Apache

You can control the server in the following ways.

  1. Stopping the server when it’s running:

    sudo systemctl stop httpd

  2. Start the server when it’s stopped:

    sudo systemctl start httpd

  3. Stop and start the server when it’s running:

    sudo systemctl restart httpd

  4. Reload the configurations while the server is running without stopping it:

    sudo systemctl reload httpd

  5. You can disable Apache so that it stops and doesn’t restart again when rebooting the system:

    sudo systemctl disable httpd

  6. To re-enable Apache if it’s been disabled. This will also enable it to restart when the system reboots:

    sudo systemctl enable httpd

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on

centos web server apache

Your Feedback Is Important

Let us know if this guide was helpful to you.

Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.