WordPress Tutorial Series

The Complete Guide to Installing WordPress with Apache on Ubuntu

The Complete Guide to Installing WordPress with Apache on Ubuntu

—

by

startwordpress
in

Overview

Yes, installing WordPress with Apache involves setting up the LAMP software stack, creating a MySQL database, configuring an Apache virtual host, and running the WordPress web installer. This manual process gives you complete control over the server environment, from the PHP version and memory limits to security configurations and SSL certificates. It is the foundational method for deploying a professional WordPress site on your own VPS or dedicated server, ensuring optimal performance and security from the ground up.

Why Choose Apache for Your WordPress Installation?

Apache remains one of the most reliable and flexible web servers for running WordPress. Its extensive module system and mature .htaccess processing make it particularly well-suited for WordPress's permalink structure and dynamic content generation. Choosing Apache means you have access to a vast ecosystem of community support and documented configurations for virtually any requirement you might have.

The main advantage of a manual Apache installation is granular control. You decide which PHP modules are active, set specific php.ini values for memory and execution time, and define precise Apache directives for security and performance. This is distinct from using a one-click installer or a control panel, which often configures a "good enough" default that may not be tuned for your specific workload. For developers, agencies, or anyone learning server administration, this method provides invaluable insight into how WordPress interacts with the underlying server infrastructure.

What You Need Before Starting

Gather these prerequisites to ensure a smooth installation:

  • A Linux server running a supported distribution like Ubuntu 22.04 or 24.04 LTS with root or sudo access.
  • A registered domain name with DNS A records pointing to your server's public IP address.
  • SSH client access to your server from your local computer.
  • Basic familiarity with using a terminal and editing files from the command line.

If your server runs a Red Hat-based distribution like CentOS or Rocky Linux, be aware that the package manager is yum or dnf, not apt. Should you encounter a "Not enough cached data to install" error, it typically signals outdated repository mirrors. The fix involves replacing the repository configuration with a working mirror and rebuilding the package cache—a solution detailed in this guide on resolving yum repository cache errors.

Step 1: Update System and Install the LAMP Stack

Begin with a fully updated system to patch security vulnerabilities and ensure package compatibility. Then, install Apache, MariaDB (a drop-in MySQL replacement), and PHP along with essential modules.

sudo apt update && sudo apt upgrade -y
sudo apt install apache2 mariadb-server \
 php libapache2-mod-php php-mysql php-curl php-gd \
 php-mbstring php-xml php-zip php-intl -y

Enable the Apache rewrite module, which is essential for WordPress to use clean, human-readable permalinks:

sudo a2enmod rewrite
sudo systemctl restart apache2

Secure your database installation by running the interactive script. Follow the prompts to set a strong root password, remove anonymous test users, and disable remote root login:

sudo mysql_secure_installation

Step 2: Decide on PHP Processing Method

For a single-site installation, you have two primary methods for processing PHP with Apache. Choosing the right one depends on your performance needs and administrative preferences.

Method How It Works Pros Cons
mod_php (libapache2-mod-php) PHP is loaded as an Apache module. Simple to set up. Good compatibility. Uses more RAM per process. Less control over PHP worker pool.
PHP-FPM PHP runs as a separate FastCGI process manager. Better performance under load. More granular control over workers. Lower memory footprint per request. Slightly more complex configuration. Requires managing a separate service.

For most production websites aiming for good performance, PHP-FPM is the recommended choice. The installation is straightforward on Ubuntu:

sudo apt install php-fpm -y
sudo systemctl enable --now php-fpm

Enable the necessary Apache modules to proxy requests to PHP-FPM and restart Apache:

sudo a2enmod proxy_fcgi setenvif
sudo a2enconf php*-fpm # The asterisk matches your installed version
sudo systemctl restart apache2

If you later need to adjust PHP settings like memory_limit or upload_max_filesize, you will edit the PHP-FPM pool configuration (e.g., /etc/php/8.3/fpm/pool.d/www.conf) and restart the PHP-FPM service, not Apache.

Step 3: Create the WordPress Database and User

Each WordPress site requires its own database. Log into the MySQL console as the root user:

sudo mysql -u root -p

Create a new database, a dedicated user with a strong password, and grant that user full privileges on the database:

CREATE DATABASE wordpress_db;
CREATE USER 'wp_user'@'localhost' IDENTIFIED BY 'Your_Strong_Password_Here!';
GRANT ALL PRIVILEGES ON wordpress_db.* TO 'wp_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Replace Your_Strong_Password_Here! with a real, complex password. Using a dedicated database user for WordPress, instead of the root user, is a fundamental security practice.

Step 4: Create the Apache Virtual Host Configuration

The virtual host file tells Apache where to find the website files for your domain. Create a new configuration file for your site:

sudo nano /etc/apache2/sites-available/yourdomain.com.conf

Paste the following configuration, adjusting the ServerName, ServerAlias, and DocumentRoot path. The AllowOverride All directive is critical—it enables WordPress's .htaccess file to manage permalinks and other rules.

<VirtualHost *:80>
 ServerName yourdomain.com
 ServerAlias www.yourdomain.com
 DocumentRoot /var/www/yourdomain.com

 <Directory /var/www/yourdomain.com>
 AllowOverride All
 Require all granted
 </Directory>

 ErrorLog ${APACHE_LOG_DIR}/yourdomain_error.log
 CustomLog ${APACHE_LOG_DIR}/yourdomain_access.log combined
</VirtualHost>

Enable the site, disable the default placeholder, and reload Apache:

sudo a2ensite yourdomain.com.conf
sudo a2dissite 000-default.conf
sudo systemctl reload apache2

Step 5: Download WordPress and Set Correct Permissions

Navigate to the temporary directory, download the latest WordPress archive, and extract it:

cd /tmp
sudo wget
sudo tar -xzf latest.tar.gz

Move the WordPress files into the directory you defined as the DocumentRoot in your virtual host:

sudo mv /tmp/wordpress/* /var/www/yourdomain.com/

Assign ownership of the files to the Apache web server user (www-data) so it can write to directories like wp-content for updates and media uploads:

sudo chown -R www-data:www-data /var/www/yourdomain.com

Step 6: Configure wp-config.php and Run the Installer

Create the WordPress configuration file by copying the sample:

sudo cp /var/www/yourdomain.com/wp-config-sample.php /var/www/yourdomain.com/wp-config.php

Edit the file to input your database details:

sudo nano /var/www/yourdomain.com/wp-config.php

Locate the database settings and fill them in:

  • DB_NAME: The database name you created (wordpress_db).
  • DB_USER: The database user you created (wp_user).
  • DB_PASSWORD: The password you set for that user.

Next, generate unique security salts. WordPress provides a tool for this. Copy the entire block of generated keys and paste them into your wp-config.php file, replacing the placeholder values.

Save and close the file. Now, open your web browser and visit `. You will see the WordPress installation screen. Follow the on-screen prompts to set your site title, administrator username, password, and email. Click "Install WordPress" to complete the setup.

Step 7: Secure Your Site with SSL/HTTPS

An SSL certificate is no longer optional; it protects data in transit and is required for browser trust and SEO. Let's Encrypt provides free, automated certificates. Install Certbot:

sudo apt install certbot python3-certbot-apache -y

Obtain and install a certificate for your domain. Certbot will automatically configure Apache for HTTPS and set up HTTP to HTTPS redirects:

sudo certbot --apache -d yourdomain.com -d www.yourdomain.com

Follow the interactive prompts. Certbot will also set up a cron job to renew your certificate before it expires.

Post-Installation Checklist

After installation, run through this quick checklist to ensure a solid foundation:

  • Confirm your site loads correctly over `.
  • Log into the WordPress Dashboard and delete the default "Hello World" post and sample page.
  • Navigate to Settings > Permalinks and select your desired structure (e.g., "Post name") to flush rewrite rules.
  • Install a caching plugin to optimize performance.
  • Review and configure basic security settings in the Dashboard.
  • Set up a regular backup routine for both your files and database.

Common Questions

Can I host multiple WordPress sites on the same Apache server?

Yes, absolutely. This is done by creating an additional Apache virtual host configuration file for each new domain, pointing it to a new directory under /var/www/, and creating a separate MySQL database for each site. The process mirrors the single-site setup for each additional installation.

Do I need a control panel like cPanel to install WordPress?

No, you do not need a control panel. The manual installation process outlined above gives you full control without the overhead or cost of a control panel. However, a panel can simplify some tasks like database management and cron job setup for users less comfortable with the command line.

What are the most important security steps after installation?

After installation, immediately ensure you are using strong, unique passwords for both your WordPress admin user and your database user. Keep WordPress core, themes, and plugins updated. Install a security plugin to limit login attempts and monitor files. Finally, confirm your SSL certificate is active and forces HTTPS for all traffic.

How can I improve WordPress performance on Apache?

Key performance improvements include using PHP-FPM over mod_php, installing an object caching plugin (like Redis or Memcached), using a full-page caching plugin, optimizing your images before upload, and ensuring your database is regularly cleaned of post revisions and transient options.

What should I do if I see a "500 Internal Server Error"?

This generic error often points to a problem with file permissions or the .htaccess file. First, check your Apache error log (/var/log/apache2/error.log) for a specific message. Ensure the wp-content directory is writable by the web server. You can try renaming the existing .htaccess file via SSH to see if the site loads; if it does, permalink settings likely need to be reset in the Dashboard.

Conclusion

Installing WordPress with Apache manually provides a transparent, powerful, and highly customizable foundation for any website. By following these steps, you gain direct control over every layer of the stack, from the server configuration to the WordPress core. This knowledge is invaluable for troubleshooting, performance tuning, and security hardening as your site grows.

For those seeking a streamlined start, exploring WordPress-optimized hosting plans that provide pre-configured LAMP environments can save time while retaining flexibility. Alternatively, if you prefer to focus solely on content and business logic, a managed WordPress hosting solution removes the server administration overhead entirely, allowing you to deploy your site quickly and let the provider handle security, updates, and performance optimization.