Admin: New server guide

2026-04-12T15:56:05Z

New server guide

New page

= Installing Apache Web Server =

This guide provides a comprehensive walkthrough for installing and configuring the Apache HTTP Server (httpd) on a Linux system. We will cover basic installation, setting up virtual hosts for multiple websites, enabling URL rewriting with `mod_rewrite`, and securing your server with SSL/TLS certificates. This tutorial is suitable for beginners to intermediate Linux system administrators.

== Prerequisites ==

Before you begin, ensure you have the following:

* A Linux server with root or sudo privileges. Dedicated servers from [https://powervps.net/?from=32 PowerVPS] offer the full root access needed for these operations.
* Internet connectivity to download packages.
* Basic understanding of the Linux command line.
* (Optional) A domain name pointing to your server's IP address.

== Step 1: Installing Apache HTTP Server ==

The installation process varies slightly depending on your Linux distribution.

=== For Debian/Ubuntu-based systems ===

Use the Advanced Package Tool (APT) to install Apache:

<pre>
sudo apt update
sudo apt install apache2 -y
</pre>

=== For RHEL/CentOS/Fedora-based systems ===

Use the YUM or DNF package manager:

<pre>
sudo yum update -y
sudo yum install httpd -y
# Or for newer Fedora/RHEL versions:
# sudo dnf update -y
# sudo dnf install httpd -y
</pre>

After installation, start and enable the Apache service to run on boot:

<pre>
# For Debian/Ubuntu
sudo systemctl start apache2
sudo systemctl enable apache2

# For RHEL/CentOS/Fedora
sudo systemctl start httpd
sudo systemctl enable httpd
</pre>

Verify the status of the Apache service:

<pre>
# For Debian/Ubuntu
sudo systemctl status apache2

# For RHEL/CentOS/Fedora
sudo systemctl status httpd
</pre>

You should see output indicating the service is "active (running)".

=== Firewall Configuration ===

If you have a firewall enabled (e.g., `ufw` or `firewalld`), you need to allow HTTP and HTTPS traffic.

==== Using UFW (Debian/Ubuntu) ====

<pre>
sudo ufw allow 'Apache Full'
sudo ufw enable
sudo ufw status
</pre>

==== Using Firewalld (RHEL/CentOS/Fedora) ====

<pre>
sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https
sudo firewall-cmd --reload
sudo firewall-cmd --list-all
</pre>

Now, open your web browser and navigate to your server's IP address (e.g., `http://your_server_ip`). You should see the default Apache welcome page.

== Step 2: Configuring Virtual Hosts ==

Virtual hosts allow you to host multiple websites on a single server. Each website will have its own configuration file.

=== Create Directory Structure ===

For each website, create a dedicated directory for its files. It's common practice to place these in `/var/www/`.

Let's assume you want to host `example.com` and `blog.example.com`.

<pre>
sudo mkdir -p /var/www/example.com/public_html
sudo mkdir -p /var/www/blog.example.com/public_html
</pre>

=== Set Permissions ===

Ensure Apache has the necessary permissions to access these directories.

<pre>
sudo chown -R $USER:$USER /var/www/example.com/public_html
sudo chown -R $USER:$USER /var/www/blog.example.com/public_html
sudo chmod -R 755 /var/www/
</pre>

Create a sample `index.html` file for each site:

<pre>
echo "<h1>Welcome to example.com!</h1>" | sudo tee /var/www/example.com/public_html/index.html
echo "<h1>Welcome to blog.example.com!</h1>" | sudo tee /var/www/blog.example.com/public_html/index.html
</pre>

=== Create Virtual Host Configuration Files ===

Apache's virtual host configurations are typically stored in `/etc/apache2/sites-available/` (Debian/Ubuntu) or `/etc/httpd/conf.d/` (RHEL/CentOS/Fedora).

==== For Debian/Ubuntu ====

Create a new configuration file for `example.com`:

<pre>
sudo nano /etc/apache2/sites-available/example.com.conf
</pre>

Paste the following content, replacing `example.com` with your domain and `your_server_ip` with your server's IP address:

<pre>
<VirtualHost *:80>
ServerAdmin webmaster@example.com
ServerName example.com
ServerAlias www.example.com
DocumentRoot /var/www/example.com/public_html
ErrorLog ${APACHE_LOG_DIR}/example.com_error.log
CustomLog ${APACHE_LOG_DIR}/example.com_access.log combined
</VirtualHost>
</pre>

Create a similar file for `blog.example.com`:

<pre>
sudo nano /etc/apache2/sites-available/blog.example.com.conf
</pre>

Paste the following content:

<pre>
<VirtualHost *:80>
ServerAdmin webmaster@blog.example.com
ServerName blog.example.com
DocumentRoot /var/www/blog.example.com/public_html
ErrorLog ${APACHE_LOG_DIR}/blog.example.com_error.log
CustomLog ${APACHE_LOG_DIR}/blog.example.com_access.log combined
</VirtualHost>
</pre>

Enable the new virtual host configurations and disable the default one:

<pre>
sudo a2ensite example.com.conf
sudo a2ensite blog.example.com.conf
sudo a2dissite 000-default.conf
</pre>

==== For RHEL/CentOS/Fedora ====

Create a new configuration file for `example.com` in the `conf.d` directory:

<pre>
sudo nano /etc/httpd/conf.d/example.com.conf
</pre>

Paste the following content:

<pre>
<VirtualHost *:80>
ServerAdmin webmaster@example.com
ServerName example.com
ServerAlias www.example.com
DocumentRoot /var/www/example.com/public_html
ErrorLog /var/log/httpd/example.com_error.log
CustomLog /var/log/httpd/example.com_access.log combined
</VirtualHost>
</pre>

Create a similar file for `blog.example.com`:

<pre>
sudo nano /etc/httpd/conf.d/blog.example.com.conf
</pre>

Paste the following content:

<pre>
<VirtualHost *:80>
ServerAdmin webmaster@blog.example.com
ServerName blog.example.com
DocumentRoot /var/www/blog.example.com/public_html
ErrorLog /var/log/httpd/blog.example.com_error.log
CustomLog /var/log/httpd/blog.example.com_access.log combined
</VirtualHost>
</pre>

=== Test and Reload Apache ===

Before applying the changes, test your Apache configuration for syntax errors:

<pre>
# For Debian/Ubuntu
sudo apache2ctl configtest

# For RHEL/CentOS/Fedora
sudo httpd -t
</pre>

If the syntax is OK, reload Apache to apply the new virtual hosts:

<pre>
# For Debian/Ubuntu
sudo systemctl reload apache2

# For RHEL/CentOS/Fedora
sudo systemctl reload httpd
</pre>

Now, if you have your DNS records set up correctly, `example.com` and `blog.example.com` should point to their respective content.

== Step 3: Enabling mod_rewrite ==

The `mod_rewrite` module allows for powerful URL manipulation, often used for SEO-friendly URLs or redirecting traffic.

=== Enable the Module ===

==== For Debian/Ubuntu ====

<pre>
sudo a2enmod rewrite
sudo systemctl restart apache2
</pre>

==== For RHEL/CentOS/Fedora ====

`mod_rewrite` is usually enabled by default. If not, you might need to uncomment a `LoadModule rewrite_module modules/mod_rewrite.so` line in your main Apache configuration file (e.g., `/etc/httpd/conf/httpd.conf`). After enabling, reload Apache:

<pre>
sudo systemctl reload httpd
</pre>

=== Configure .htaccess ===

To use `mod_rewrite` rules, you need to allow `.htaccess` files to override server configurations. Edit your virtual host configuration files and add `AllowOverride All` within the `<Directory>` block for your `public_html` directories.

For `example.com.conf` (Debian/Ubuntu):
<pre>
<Directory /var/www/example.com/public_html>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</pre>

For `example.com.conf` (RHEL/CentOS/Fedora):
<pre>
<Directory "/var/www/example.com/public_html">
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</pre>

Repeat this for `blog.example.com`. After making changes, test and reload Apache.

=== Example .htaccess Rule ===

Create a `.htaccess` file in your `public_html` directory:

<pre>
echo "RewriteEngine On
RewriteRule ^new-page$ /old-page.html [R=301,L]" | sudo tee /var/www/example.com/public_html/.htaccess
</pre>

This rule will redirect requests for `/new-page` to `/old-page.html` with a permanent (301) redirect.

== Step 4: Securing Apache with SSL/TLS ==

Securing your websites with HTTPS is crucial for data privacy and trust. We'll use Let's Encrypt for free SSL certificates.

=== Install Certbot ===

Certbot is a tool that automates the process of obtaining and renewing Let's Encrypt certificates.

==== For Debian/Ubuntu ====

<pre>
sudo apt update
sudo apt install certbot python3-certbot-apache -y
</pre>

==== For RHEL/CentOS/Fedora ====

First, ensure you have the EPEL repository enabled.

<pre>
sudo yum install epel-release -y
sudo yum install certbot python3-certbot-apache -y
# Or for newer Fedora/RHEL versions:
# sudo dnf install epel-release -y
# sudo dnf install certbot python3-certbot-apache -y
</pre>

=== Obtain SSL Certificates ===

Run Certbot to get certificates for your domains. Make sure your domain's DNS records are pointing to your server's IP address.

<pre>
sudo certbot --apache -d example.com -d www.example.com -d blog.example.com
</pre>

Follow the on-screen prompts. Certbot will automatically detect your virtual hosts, obtain certificates, and configure Apache to use them. It will also set up automatic renewal.

=== Verify SSL Configuration ===

After running Certbot, your sites should be accessible via HTTPS. You can verify this by visiting `https://example.com` in your browser. Look for the padlock icon.

Certbot typically modifies your virtual host files to include SSL configurations and redirects HTTP traffic to HTTPS.

== Troubleshooting ==

* '''Apache not starting:''' Check the Apache error logs (`/var/log/apache2/error.log` or `/var/log/httpd/error_log`) for specific messages. Common issues include syntax errors in configuration files or port conflicts.
* '''Virtual hosts not working:'''
* Ensure DNS records are correctly pointing to your server's IP.
* Verify that your virtual host configuration files are enabled (e.g., using `a2ensite` on Debian/Ubuntu).
* Check file permissions for your web root directories.
* Confirm that `ServerName` directives match the domains you are testing.
* '''SSL certificate errors:'''
* Ensure Certbot ran successfully and that you followed all prompts.
* Check that your domain's DNS is pointing to the correct IP address.
* Verify that port 80 is open for the initial Let's Encrypt challenge.
* Run `sudo certbot renew --dry-run` to test the renewal process.
* '''mod_rewrite not working:'''
* Ensure `mod_rewrite` is enabled.
* Verify that `AllowOverride All` is set in the relevant `<Directory>` block in your Apache configuration.
* Check your `.htaccess` file for syntax errors.

== Related Articles ==

* [[Firewall Configuration]]
* [[DNS Management]]
* [[Securing Linux Servers]]

[[Category:Web Server Setup]]
[[Category:Apache]]
[[Category:Linux Administration]]

{{Exchange Box}}

Installing Apache Web Server - Revision history

Admin: New server guide