WordPress Multisite on VPS: network of sites, installation, and hosting

What is WordPress Multisite and How Does It Work?

WordPress Multisite on a VPS is a powerful solution that allows you to host an entire network of independent WordPress sites on a single WordPress instance and a single Virtual Private Server, providing centralized management, resource savings, and high flexibility for developers, agencies, and large projects. This functionality, built into the core of WordPress, transforms a regular installation into a scalable platform for hosting multiple sites, each of which can have its own unique domain, subdomain, or subdirectory.

Essentially, WordPress Multisite creates a single administrative dashboard from which a "Super Admin" can manage the entire network. This includes adding and deleting sites, managing network users, installing and updating plugins and themes for all sites, and controlling general settings. At the same time, each individual site in the network retains its own database (or set of tables within a shared database), media files, users, and can even have its own administrators who manage only their site without access to global network settings.

Technically, WordPress Multisite uses a single MySQL database, but for each individual site, unique tables are created within it with a prefix, for example, wp_2_posts, wp_3_users, and so on, if the main site uses the wp_ prefix. This allows the data of each site to be stored in isolation but within a single DBMS, which simplifies backup and management. WordPress core files, plugins, and themes are also shared across the entire network, significantly saving disk space and simplifying the update process.

Key Components of a WordPress Multisite Network

To understand how a WordPress Multisite network works, it's important to know its key elements:

• Super Admin: This is the user with the highest privileges who manages the entire network. They can install and delete themes and plugins for the entire network, create and delete sites, assign administrators to individual sites, and control global settings.
• Sites: Each individual web resource in the network is a "site." It has its own URL, administrative panel, users, posts, pages, and media files. Individual site administrators can activate available themes and plugins, and manage their site's content and users.
• Network Themes & Plugins: Themes and plugins are installed by the Super Admin for the entire network. Once installed, they become available for activation on any site in the network. The Super Admin can also "Network Activate" a plugin, which will make it mandatory and active on all sites without the possibility of deactivation by local administrators.
• Shared Database: All sites in the network use the same MySQL database, but with different table prefixes for each site, ensuring logical data isolation.
• Shared File System: The WordPress core, as well as all installed themes and plugins, are stored in a single directory, which reduces file duplication and simplifies maintenance.

Advantages and Disadvantages of Using Multisite

Advantages:

• Centralized Management: One login to the admin panel to manage all sites. Install and update themes/plugins once for the entire network.
• Resource Savings: Less disk space and memory, as WordPress core, themes, and plugins are not duplicated.
• Easy Scalability: Easily add new sites to the network, ideal for fast-growing projects or client portals.
• Consistency: Ability to ensure a uniform set of plugins and themes, as well as security standards for all sites in the network.
• Convenience for Developers: Developing and testing plugins/themes for the entire network becomes simpler.

Disadvantages:

• Setup and Administration Complexity: Setting up WordPress Multisite, especially on a VPS, requires certain technical knowledge in web servers, DNS, and command-line operations.
• Single Point of Failure: If the main site or network database goes down, it affects all sites.
• Plugin Dependency: Not all plugins are fully compatible with Multisite. Some may not work correctly or require separate licenses for each site.
• Performance Issues: One poorly optimized site or plugin can negatively impact the performance of the entire network. Careful WordPress Multisite hosting with sufficient resources is required.
• Backup: Backing up the entire network can be more complex than for a single site, although specialized plugins and methods exist.

When to Use a WordPress Multisite Network?

The decision to switch to WordPress Multisite or deploy a new network of sites based on it should be well-considered. This functionality is not a universal solution for every case where multiple sites are needed. However, in certain scenarios, it offers significant advantages in management, scalability, and resource savings.

Typical Use Cases

A WordPress Multisite network is ideal for the following cases:

• Educational Institutions: Universities, schools, or colleges can provide each faculty, department, or even student club with its own site, managed centrally.
• Large Corporations with Subsidiaries or Departments: Each division can have its own website, while maintaining a unified brand and structure, managed by the IT department.
• News Portals or Magazines: Different sections or authors can have their blogs/sections, united in one network.
• Web Agencies: Agencies can use Multisite to host and manage their clients' websites, offering them limited access to their site's admin panel, while maintaining full control over updates and security at the network level.
• Directory Sites or User-Generated Content Portals: For example, a real estate directory where each realtor gets their mini-site, or a social network where users can create their own blogs.
• Multilingual Sites: Each language can be a separate site in the network, simplifying content and language version management.
• SaaS Platforms on WordPress: If you offer a service where users can create their own websites (e.g., a blog builder), Multisite is an ideal foundation.

In these cases, centralized management of updates, plugins, and themes, as well as the ability to quickly create new sites, significantly simplify workflows and reduce operational costs. If you are launching multiple projects that require similar basic functionality and are united by a common logic, WordPress Multisite on a reliable VPS can be your choice.

Alternatives and When They Are Preferable

Despite all the advantages, there are situations where WordPress Multisite may not be the best solution:

• Completely Independent Projects: If your sites have nothing in common other than being built on WordPress, and are managed by different teams without the need for centralized control, then separate WordPress installations on different subdomains or domains would be preferable. This eliminates a "single point of failure" and gives each project full autonomy.
• Different Plugin/Theme Requirements: If each site requires a unique set of plugins and themes that differ significantly from each other, managing them within Multisite can become cumbersome. Some plugins may conflict or require specific configuration for each site, which negates the benefits of centralization.
• High Security and Isolation Requirements: If the compromise of one site in the network could have critical consequences for others (e.g., for banking or government institutions), then complete isolation at the level of separate VPS or even managed dedicated servers might be a safer option.
• Limited Technical Knowledge: If you or your team lack experience with servers, DNS, and more complex WordPress configurations, supporting Multisite might be too challenging. In this case, using several separate installations on regular hosting or a managed VPS would be simpler.

It is important to weigh all the pros and cons based on the specific needs of your project. Sometimes the simplicity of several separate installations outweighs the potential benefits of centralization.

Preparing a VPS for WordPress Multisite: Hosting Selection and Preliminary Setup

Successful deployment of WordPress Multisite on a VPS begins with the right hosting choice and proper preliminary server setup. Since a network of sites can consume significantly more resources than a single standard WordPress site, it is crucial to ensure sufficient performance and stability.

Choosing the Optimal VPS Plan for Multisite

When choosing a VPS for WordPress Multisite hosting, you should pay attention to several key parameters:

1. Processor (CPU): For a small network (up to 10-15 sites with moderate traffic), 2-4 vCPUs will be sufficient. For medium to large networks (up to 50 sites or with high traffic), 4-8 vCPUs are recommended. For very large networks or high-load projects, 8+ vCPUs or even a dedicated server may be required.
2. Random Access Memory (RAM): This is one of the most critical resources.
   • Minimum: 2 GB RAM for a network of 2-3 sites with low traffic.
   • Recommended: 4-8 GB RAM for most medium networks (up to 20-30 sites).
   • Optimal: 16 GB RAM or more for large networks, especially if resource-intensive plugins, many users, or high traffic are involved.
   Remember that each active PHP process, database, and web server consumes RAM.
3. Disk Space (Storage): Choose NVMe drives. They provide significantly higher read/write speeds compared to SSDs or HDDs, which is critical for WordPress performance, especially with a large number of small files (images, cache) and active database operations.
   • Minimum: 80-100 GB NVMe to start.
   • Recommended: 160-250 GB NVMe to have room for media files, backups, and growth.
4. Bandwidth: Ensure your plan includes sufficient traffic volume (e.g., 1-2 TB/month) and a high port speed (1 Gbps or more).
5. Geographic Location of Your VPS: Choose a data center located closer to your primary audience to minimize latency and speed up site loading.

For example, for a network of 10-20 sites with moderate traffic, a VPS plan with 4-6 vCPUs, 8 GB RAM, and 160 GB NVMe would be a good starting point. Valebyte.com offers various VPS plans that can be scaled as your network grows.

Basic Server Setup: OS, Web Server, Database

After choosing a VPS, you need to set up the basic server environment. We recommend using a Linux-based operating system, such as Ubuntu Server (LTS version) or Debian, due to their stability, broad community support, and extensive documentation.

1. System Update: Always start by updating the package manager and installed packages:

   sudo apt update
   sudo apt upgrade -y

2. Web Server Installation:
   • Nginx (recommended): Known for its performance and efficiency in handling static content and as a reverse proxy.

     sudo apt install nginx -y

     Example basic Nginx configuration (for subdomains, considering PHP-FPM):

     server {
         listen 80;
         server_name example.com *.example.com; # Replace with your main domain
         root /var/www/html/wordpress; # Path to your WordPress installation
     
         index index.php index.html index.htm;
     
         location / {
             try_files $uri $uri/ /index.php?$args;
         }
     
         location ~ \.php$ {
             include snippets/fastcgi-php.conf;
             fastcgi_pass unix:/var/run/php/php8.1-fpm.sock; # Specify your PHP-FPM version
             fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
             include fastcgi_params;
         }
     
         # For subdomains in Multisite
         location ~ /\. {
             deny all;
         }
     
         # Protection against direct file access
         location ~* /(wp-content|wp-includes|wp-admin|uploads|themes|plugins)/.*\.(php|phps|phtml|py|rb|sh|bash|ini|log)$ {
             deny all;
         }
     }

   • Apache: Easier to configure for Multisite due to the .htaccess file, but may be less performant under high load.

     sudo apt install apache2 -y

3. PHP and PHP-FPM Installation: WordPress requires PHP. For better performance, use PHP-FPM. PHP 8.1 or higher is recommended.

   sudo apt install php8.1 php8.1-fpm php8.1-mysql php8.1-curl php8.1-gd php8.1-mbstring php8.1-xml php8.1-zip php8.1-imagick -y

   After installing PHP-FPM, if using Nginx, ensure its configuration points to the PHP-FPM socket (as in the example above). If using Apache, ensure the mod_php or mod_fcgid/mod_proxy_fcgi module is configured correctly.
4. MySQL/MariaDB Database Installation: WordPress uses MySQL or a compatible DBMS. MariaDB is an excellent alternative.

   sudo apt install mariadb-server -y
   sudo mysql_secure_installation # Run to configure MySQL security

   Create a new database and user for WordPress:

   sudo mysql -u root -p
   CREATE DATABASE wordpress_multisite_db;
   CREATE USER 'wordpress_user'@'localhost' IDENTIFIED BY 'your_strong_password';
   GRANT ALL PRIVILEGES ON wordpress_multisite_db.* TO 'wordpress_user'@'localhost';
   FLUSH PRIVILEGES;
   EXIT;

5. Permissions Setup: Ensure the web server has read/write permissions to the WordPress directory.

   sudo chown -R www-data:www-data /var/www/html/wordpress
   sudo chmod -R 755 /var/www/html/wordpress

   (Replace /var/www/html/wordpress with your WordPress path.)

After completing these steps, your VPS will be ready for WordPress installation and Multisite activation. Remember that for other complex web applications like Flarum, or even for game servers, as described in our articles on installing game servers, for example, Palworld, basic VPS preparation is always the first and most crucial step.

Step-by-Step WordPress Multisite Installation on a VPS

Installing WordPress Multisite on a VPS involves several key stages: first, a regular WordPress installation, then activating Multisite mode, and finally configuring the web server and WordPress configuration files. Follow these instructions to properly set up your network of sites.

Installing Standard WordPress and Configuring wp-config.php

1. Download and Unpack WordPress: Navigate to your web server's directory (e.g., /var/www/html/) and download the latest version of WordPress:

cd /var/www/html/
sudo wget https://wordpress.org/latest.tar.gz
sudo tar -xvzf latest.tar.gz
sudo mv wordpress/* . # Move files to the root folder if needed
sudo rm -rf wordpress latest.tar.gz

Ensure permissions are set correctly (see previous section).

2. Create wp-config.php: Copy the sample configuration file:

sudo cp wp-config-sample.php wp-config.php

Open wp-config.php in a text editor (e.g., nano or vim):

sudo nano wp-config.php

3. Configure Database Settings: Replace the values for DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST with the credentials you created earlier:

define( 'DB_NAME', 'wordpress_multisite_db' );
define( 'DB_USER', 'wordpress_user' );
define( 'DB_PASSWORD', 'your_strong_password' );
define( 'DB_HOST', 'localhost' );

4. Add Unique Security Keys: Generate new keys from the official WordPress website and paste them into the wp-config.php file.

5. Complete WordPress Installation via Web Interface: Open your domain in a browser (e.g., http://yourdomain.com). You will see the WordPress welcome page. Follow the instructions to create the main site of the network, specifying the site title, username, password, and email.

Activating Multisite Mode and .htaccess Configuration

After successfully installing standard WordPress, you are ready to activate WordPress Multisite:

1. Allow Multisite in wp-config.php: Open wp-config.php and add the following line before the line /* That's all, stop editing! Happy publishing. */:

define( 'WP_ALLOW_MULTISITE', true );

Save and close the file.

2. Refresh the Admin Panel Page: Log in to your WordPress site's admin panel. Go to Tools -> Network Setup. If you don't see this option, you might not have added WP_ALLOW_MULTISITE in the correct place or haven't refreshed the page.

3. Choose Network Structure: On the "Network Setup" page, you will be prompted to choose between "Sub-domains" and "Sub-directories".

• Sub-domains (e.g., site1.yourdomain.com): Require Wildcard DNS setup and web server configuration. Recommended for new installations.
• Sub-directories (e.g., yourdomain.com/site1): Do not require Wildcard DNS, but may have limitations if your WordPress installation is older than one month (WordPress prevents the use of subdirectories for older installations to avoid conflicts with existing posts).

Make your choice. Enter the network title and network admin email. Click "Install".

4. Update wp-config.php and .htaccess: After clicking "Install", WordPress will generate two blocks of code. You need to copy them and paste:

• The first block of code should be pasted into wp-config.php below the line define( 'WP_ALLOW_MULTISITE', true ); and before /* That's all, stop editing! Happy publishing. */. It will look something like this:

  define('MULTISITE', true);
  define('SUBDOMAIN_INSTALL', true); // Or false if you chose subdirectories
  define('DOMAIN_CURRENT_SITE', 'yourdomain.com');
  define('PATH_CURRENT_SITE', '/');
  define('SITE_ID_CURRENT_SITE', 1);
  define('BLOG_ID_CURRENT_SITE', 1);

• The second block of code will replace the content of your .htaccess file (for Apache) or be used for Nginx configuration (for Nginx). For Apache: Open .htaccess in the WordPress root directory:

  sudo nano .htaccess

  Replace all content of the file with the provided code, which will look something like this:

  RewriteEngine On
  RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  RewriteBase /
  RewriteRule ^index\.php$ - [L]
  
  # add a trailing slash to /wp-admin
  RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
  
  RewriteCond %{REQUEST_FILENAME} -f [OR]
  RewriteCond %{REQUEST_FILENAME} -d
  RewriteRule ^ - [L]
  RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
  RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
  RewriteRule . index.php [L]

  For Nginx: If you are using Nginx, you will need to manually configure your virtual host configuration file (e.g., /etc/nginx/sites-available/yourdomain.com) according to the instructions WordPress provides on this page. This will include try_files and rewrite directives to correctly handle requests to subdomains or subdirectories. An example for subdomains was provided in the previous section.

5. Re-login: After saving changes to wp-config.php and .htaccess, WordPress will ask you to log in again. Your WordPress Multisite network is now activated. You will see "My Sites" in the top admin bar, from where you can manage the network and individual sites.

Subdomains vs. Subdirectories: What to Choose for Your WordPress Site Network?

One of the first and most important decisions when setting up WordPress Multisite is choosing the URL structure for your network: whether to use subdomains (e.g., site1.maindomain.com) or subdirectories (e.g., maindomain.com/site1). This choice affects SEO, ease of setup, and flexibility for future development.

Advantages and Disadvantages of Each Approach

Subdomains:

Example: blog.example.com, shop.example.com

Advantages:

• SEO Benefits: Search engines are believed to treat subdomains as more independent entities than subdirectories, which can be beneficial if each site in your network has a very different topic.
• Flexibility for Domain Mapping: Subdomains are easier to integrate with domain mapping functionality, allowing each network site to have its own unique domain (e.g., site1.com instead of site1.maindomain.com).
• Clear Separation: Visually and logically, subdomains create a sense of greater independence for each site.
• Easy Setup for New Installations: WordPress recommends subdomains for fresh Multisite installations.

Disadvantages:

• Requires Wildcard DNS: To support subdomains, you need to configure a Wildcard DNS record (*.example.com, pointing to your VPS's IP). This can be more complex for beginners.
• Web Server Configuration: Requires specific Nginx or Apache configuration to properly route requests to subdomains.
• SSL Certificates: Each subdomain or the entire network will require a Wildcard SSL certificate (e.g., Let's Encrypt Wildcard), which adds complexity to the setup.

Subdirectories:

Example: example.com/blog, example.com/shop

Advantages:

• Ease of Setup: Do not require Wildcard DNS. Web server configuration is usually simpler, as all sites are within the same root directory of the main domain.
• SEO Benefits (for some cases): Search engines may consider content in subdirectories as part of the main domain, which can help strengthen the main domain's authority. Ideal if all sites are closely related thematically.
• One SSL Certificate: A single SSL certificate for the main domain is sufficient to cover all subdirectories.

Disadvantages:

• WordPress Limitations: WordPress does not allow the use of subdirectories for existing installations older than one month to avoid conflicts with existing pages/posts. This makes them less flexible for migration.
• Less Independence: Sites appear as parts of one large site, which may be undesirable if you want to create the impression of separate brands.
• Potential Conflicts: Possibility of URL conflicts if subdirectory names coincide with existing pages or posts on the main site.

When to choose which:

• Choose subdomains if you are creating a new network, want to give each site a more independent look, plan to use domain mapping, or if the sites have different themes.
• Choose subdirectories if all sites are closely related to the main domain, you want to strengthen the main domain's SEO, and you need the simplest possible setup without Wildcard DNS.

Configuring DNS and Web Server for Subdomains/Subdirectories

For subdomains:

1. Wildcard DNS Setup: Go to your domain registrar's or DNS provider's DNS management panel. Add an A record (or CNAME if you are using a CDN):

Type: A
Name/Host: *
Value/Points to: Your VPS IP address

This record will direct all non-existent subdomains (e.g., site1.yourdomain.com, site2.yourdomain.com) to your VPS. DNS propagation time can take up to 24-48 hours.

2. Web Server Configuration:

• Nginx: In your virtual host configuration file (e.g., /etc/nginx/sites-available/yourdomain.com), ensure the server_name directive includes Wildcard subdomains:

  server_name yourdomain.com *.yourdomain.com;

  The rest of the Nginx configuration typically already contains the necessary try_files and rewrite rules for WordPress Multisite that you received when activating the network.
• Apache: The .htaccess file generated by WordPress already contains all the necessary RewriteRule rules for handling subdomains. Ensure the mod_rewrite module is enabled:

  sudo a2enmod rewrite
  sudo systemctl restart apache2

  Also, in your virtual host configuration (e.g., /etc/apache2/sites-available/yourdomain.com.conf), ensure AllowOverride All is set for the WordPress directory so Apache can read .htaccess.

Don't forget to restart the web server after making changes: sudo systemctl restart nginx or sudo systemctl restart apache2.

For subdirectories:

1. DNS Setup: Wildcard DNS is not required. You only need an A record for the main domain (yourdomain.com and www.yourdomain.com) pointing to your VPS's IP address.

2. Web Server Configuration:

• Nginx: Nginx configuration for subdirectories will be similar to the configuration for a single WordPress site, but with specific try_files and rewrite rules provided by WordPress when activating the network.
• Apache: The .htaccess file generated by WordPress for subdirectory mode contains all the necessary rules. Ensure mod_rewrite is enabled and AllowOverride All is set for the WordPress directory.

Also, restart the web server after changes.

The choice between subdomains and subdirectories is a fundamental decision that will affect the entire architecture of your WordPress Multisite network. Carefully consider your future needs before making a choice.

Domain Mapping in WordPress Multisite: Managing Individual Domains

One of the most powerful features of WordPress Multisite is the ability to map domains. This feature allows each individual site in your network to have its own unique domain, different from the network's main domain. For example, instead of site1.maindomain.com or maindomain.com/site1, your client or department can use clientdomain.com. This creates the impression of a completely independent site while retaining all the benefits of centralized network management.

How Domain Mapping Works

The domain mapping mechanism in WordPress Multisite is quite simple but requires proper DNS and web server configuration:

1. DNS Record: For each "mapped" domain (e.g., clientdomain.com), you need to create a DNS A-record (or CNAME) pointing to the IP address of your VPS where the WordPress Multisite hosting is located. This ensures that when a request is made to clientdomain.com, the user's browser is directed to your server.
2. Web Server: Your web server (Nginx or Apache) must be configured to handle requests for all "mapped" domains and direct them to the root directory of your WordPress installation. This is usually achieved using a Wildcard Virtual Host (for Nginx) or a universal configuration (for Apache).
3. WordPress Multisite: Within WordPress, the Super Admin adds the new domain to a specific site in the network. WordPress then uses this information to determine which site from the network should be loaded when a request is made to that domain.

Previously, domain mapping required third-party plugins, but since WordPress 4.5, this functionality is built into the core. Now, it's enough to simply add the domain in the site settings in the network admin panel.

Configuring Domain Mapping and SSL

1. DNS Configuration for Each New Domain:

For each domain you want to "map" to a site in your network, you need to create a DNS A-record pointing to your VPS's IP address. For example, for the domain clientdomain.com:

Type: A
Name/Host: @ (or clientdomain.com)
Value/Points to: Your VPS IP address

Type: A
Name/Host: www
Value/Points to: Your VPS IP address

Repeat this for all domains you want to use.

2. Web Server Configuration to Handle All Domains:

Your web server must be ready to accept requests for any domain you map.

• Nginx: Ensure that the server_name directive in your virtual host's server block (e.g., /etc/nginx/sites-available/yourdomain.com) includes both the main domain and a Wildcard for subdomains, and possibly a list of all mapped domains if you are not using a universal approach. It's best to use the Wildcard approach, which was already described for subdomains, as it allows Nginx to listen for all domains directed to your IP.

  server {
      listen 80;
      server_name yourdomain.com *.yourdomain.com clientdomain.com client2domain.com; # Add all mapped domains
      root /var/www/html/wordpress; # Path to your WordPress installation
  
      # ... rest of Nginx configuration for WordPress Multisite ...
  }

  For a more flexible approach, you can use a Wildcard in server_name, but this can complicate SSL setup for individual domains without a Wildcard SSL.
• Apache: Apache is usually more forgiving, as it will direct all requests coming to the IP address to your default Virtual Host if there is no more specific match. Ensure your Virtual Host for WordPress Multisite is the default or configured to handle all domains.

3. Adding a Domain in WordPress Multisite:

Log in to the network admin panel (as Super Admin). Go to My Sites -> Network Admin -> Sites.

• Select the site for which you want to configure mapping and click "Edit".
• In the "Site Address (URL)" field, change the URL from a subdomain/subdirectory to the new domain (e.g., from site1.maindomain.com to clientdomain.com).
• Save changes.

4. Configuring SSL for Mapped Domains:

This is a critically important step for security and SEO. For each mapped domain, you will need to install an SSL certificate.

• Let's Encrypt with Certbot: This is the most popular and free solution.

  sudo apt install certbot python3-certbot-nginx -y # For Nginx
  sudo apt install certbot python3-certbot-apache -y # For Apache

  Then run Certbot for each domain:

  sudo certbot --nginx -d clientdomain.com -d www.clientdomain.com # For Nginx
  sudo certbot --apache -d clientdomain.com -d www.clientdomain.com # For Apache

  Certbot will automatically configure your web server and obtain certificates. Repeat for each mapped domain.
• Wildcard SSL Certificate: If you are using subdomains, and each subsite should have its own subdomain (e.g., site1.maindomain.com), then a Wildcard SSL certificate (*.maindomain.com) can cover all subdomains. Let's Encrypt can also issue Wildcard certificates, but this requires using the DNS-01 verification method.

After configuring SSL, ensure all requests are redirected to HTTPS. This can be done via web server configuration or using WordPress plugins (e.g., Really Simple SSL), but server-level configuration is always preferable.

Domain mapping makes a WordPress site network incredibly flexible and powerful, allowing you to manage many diverse projects from a single server while creating unique branding for each of them.

Performance and Optimization of WordPress Multisite on a VPS

Performance is a key aspect for any web platform, and WordPress Multisite on a VPS is no exception. As the number of sites, users, and content grows, the server load increases significantly. Effective optimization is critically important to ensure fast page loading, stable operation, and a positive user experience. Our goal is to get the most out of your WordPress Multisite hosting.

Caching, CDN, and Database Optimization

1. Caching: Caching is the primary tool for improving WordPress performance.

• Object Caching: Speeds up WordPress database queries. Redis or Memcached are recommended. For Redis:

  sudo apt install redis-server -y

  Then install the Redis Object Cache plugin in WordPress and activate it at the network level. Add to wp-config.php:

  define('WP_REDIS_HOST', '127.0.0.1');
  define('WP_REDIS_PORT', 6379);
  define('WP_REDIS_PASSWORD', 'your_redis_password'); // If set
  define('WP_REDIS_DATABASE', 0); // Use different databases for different sites if needed
  define('WP_CACHE_KEY_SALT', 'your_unique_salt_prefix_'); // Important for Multisite

• Page Caching: Stores fully generated HTML pages to avoid regenerating them on every request.
  • WordPress Plugins: WP Super Cache or W3 Total Cache (requires more complex setup for Multisite). Install and configure at the network level.
  • Server-side Caching (Varnish/Nginx FastCGI Cache): A more efficient solution that operates at the web server level. Varnish HTTP Cache is a powerful reverse proxy that can significantly speed up content delivery. Nginx FastCGI Cache is also very effective and easier to set up than Varnish.
• Browser Caching: Configured at the web server level (Nginx/Apache) to tell browsers how long to store static resources (CSS, JS, images).

2. Content Delivery Network (CDN): A CDN (e.g., Cloudflare, KeyCDN, BunnyCDN) distributes your static files (images, CSS, JS) across multiple servers worldwide. This reduces the distance to the user and significantly speeds up site loading, reducing the load on your VPS. Cloudflare also offers additional security and optimization features.

3. Database Optimization:

• Regular Cleanup: Remove old post revisions, spam comments, unused transients. Plugins like WP-Optimize can help.
• Indexing: Ensure all necessary database tables are indexed for fast query execution.
• MySQL/MariaDB Configuration: Optimize the database configuration (e.g., my.cnf) for your server. Parameters like innodb_buffer_pool_size, query_cache_size (for MySQL 5.7 and below), max_connections are very important. For example, innodb_buffer_pool_size should be set to approximately 50-70% of available RAM if the database is the primary memory consumer.

4. Image Optimization: Use plugins for image compression (e.g., Smush, Imagify) and convert them to modern formats (WebP). This significantly reduces page size.

Resource Monitoring and Scaling

1. Resource Monitoring: Regular monitoring of your VPS is key to identifying bottlenecks and performance issues.

• Command-line Tools: Use htop for CPU and RAM monitoring, iotop for disk operations, netstat for network activity.
• Web Server Monitoring: Nginx Access Logs and Error Logs, Apache Access Logs and Error Logs.
• Monitoring Systems: Install a monitoring system such as Prometheus + Grafana, Netdata, Zabbix, or use cloud monitoring services. This will allow you to track CPU load, RAM usage, disk operations, network traffic, the number of active PHP processes, and database queries in real-time. Many of these tools, like monitoring tools similar to Dozzle, can be easily installed on a VPS.
• WordPress Monitoring: Use performance monitoring and debugging plugins like Query Monitor to identify slow database queries or resource-intensive plugins.

2. Scaling: As your WordPress Multisite network grows, VPS scaling may be required.

• Vertical Scaling: Increasing the resources of the current VPS (adding CPU, RAM, disk space). Valebyte.com allows easy upgrading of VPS plans.
• Horizontal Scaling (for very large networks): Separating components onto individual servers. For example, dedicating a separate VPS for the database (MySQL/MariaDB), another for caching (Redis/Memcached), and several VPS for the web server with a load balancer. This is significantly more complex and usually only required for high-load enterprise projects.
• Code Optimization: Regularly check and optimize theme and plugin code. Remove unused plugins and themes.

Remember that each site in your network contributes to the overall load. A poorly optimized plugin on one site can slow down the entire network. Therefore, it is important to monitor what individual site administrators install and, if necessary, limit their capabilities.

What VPS is Needed for WordPress Multisite: Valebyte.com Recommendations

Choosing the right VPS for WordPress Multisite is critical for the stable operation and performance of your site network. Valebyte.com offers various configurations that can meet the needs from small personal blogs to large corporate networks. Here are our recommendations, based on experience hosting demanding web applications.

Minimum and Recommended Configurations

VPS requirements for WordPress Multisite heavily depend on the number of sites in the network, their traffic, the complexity of themes and plugins used, and the number of active users. We have divided the recommendations into three levels:

1. Entry Level (for small networks, up to 5-10 sites with low traffic):

• CPU: 2 vCPU
• RAM: 4 GB
• Disk: 80-100 GB NVMe
• Bandwidth: 1 TB/month
• Example Usage: Several personal blogs, test environment, site network for a small startup.
• Note: At this level, it is critically important to use caching (Nginx FastCGI Cache or plugins) and image optimization.

2. Mid-Level (for medium networks, up to 20-50 sites with moderate traffic):

• CPU: 4-6 vCPU
• RAM: 8-16 GB
• Disk: 160-250 GB NVMe
• Bandwidth: 2-4 TB/month
• Example Usage: Site network for a web agency (client sites), corporate division network, educational portal.
• Note: Implementation of object caching (Redis/Memcached) and CDN is mandatory. Regular server resource monitoring becomes critical.

3. Advanced Level (for large networks, more than 50 sites or with high traffic/E-commerce):

• CPU: 8+ vCPU (or dedicated cores)
• RAM: 32+ GB
• Disk: 500 GB+ NVMe (or multiple disks)
• Bandwidth: 5+ TB/month
• Example Usage: Large WordPress-based SaaS platforms, big media portals, E-commerce networks requiring high availability and performance.
• Note: At this level, horizontal scaling (separate servers for DB, cache, web servers), managed hosting, and/or the use of high-performance dedicated servers are often required. Monitoring using advanced systems (Prometheus/Grafana) is mandatory.

Comparison of Valebyte.com Plans for WordPress Multisite

Here is an approximate comparison of Valebyte.com plans suitable for various levels of WordPress Multisite hosting. Please note that prices and exact specifications may change, and for up-to-date information, it is always best to visit our website.

Valebyte.com Plan	vCPU	RAM (GB)	NVMe Disk (GB)	Traffic (TB/month)	Approx. Price ($/month)	Suitable For
VPS-Start	2	4	80	1	from $15	Small networks (up to 10 sites), personal blogs, test projects
VPS-Standard	4	8	160	2	from $30	Medium networks (up to 30 sites), small agencies, corporate portals
VPS-Pro	6	16	250	4	from $60	Large networks (up to 50+ sites), high-load projects, E-commerce
VPS-Enterprise	8+	32+	500+	5+	from $120	Very large networks, SaaS platforms, critical business applications

Important Recommendations When Choosing:

1. Start with a Buffer: Always choose a plan with a slight buffer in resources to avoid performance issues during sudden traffic spikes or the addition of new sites.
2. Scalability: Ensure your provider (like Valebyte.com) offers easy scaling of VPS resources without downtime.
3. NVMe Drives: This is non-negotiable. For WordPress, especially Multisite, disk subsystem speed is paramount.
4. Support: The availability of qualified technical support to assist with server-related issues (not WordPress-specific) is very valuable.
5. Monitoring: Use built-in VPS control panel monitoring tools or third-party solutions to always be aware of your server's status.

By choosing WordPress Multisite hosting on a VPS from Valebyte.com, you get not only powerful and fast servers but also the flexibility needed for your site network to grow.

Conclusion

WordPress Multisite on a VPS represents a powerful and flexible solution for centrally managing multiple websites, offering significant resource savings and simplified administrative tasks. For successful deployment and maintenance of such a network, the choice of a suitable VPS with sufficient RAM, high-performance NVMe drives, and a powerful CPU is critical, as is careful configuration of the web server, database, and caching systems. Valebyte.com offers optimal VPS plans that can be scaled as your network grows, ensuring stability and high performance.