- Plesk Onyx for Linux
- Plesk Onyx for Windows
How to set up a WordPress multisite on the Plesk server?
Note: It is recommended to set up a network on a fresh WordPress deployment, since enabling multisite on a production website might cause some problems.
Create a new subscription in Home > Subscriptions > Add Subscription.
Install a WordPress instance for the subscription in Home > Subscriptions > example.com > Install WordPress.
Log into the WordPress instance as an administrator in Home > WordPress > example.com > Log in.
Follow the instruction and update and update
.htaccessfiles in Plesk > Subscriptions > example.com > File Manager.
Note: If FPM by nginx is set as PHP handler or website uses nginx only configuration use the following article to add addtional nginx directives:
What are nginx rewrite rules for WordPress multisite?
Relogin to the WordPress instance as an administrator in Home > WordPress > example.com > Log in.
Go to My Sites > Network Admin > Sites and create additional sites in your WordPress network. For example:
Don't be confused by the fact, that sites are configured as subdomains. They will be remapped later. Remember their IDs (can be seen in the URL when you hover your mouse over the site name) - you'll need them for mapping.
Go to Settings > Domains and define domain-site mappings, using site IDs and domain names using. For example:
Site ID can be seen in the URL when you hover your mouse over the site name (Step 5).
Leave Primary checkbox selected, otherwise WordPress will redirect visitors from a domain to the subdomain it is mapped to.
At this point, multisite set up on the WordPress side is complete. Now, it is time to create these additional websites on the Plesk side. There are three ways to do this:
Create domain aliases for the main website on the webspace (in our example, aliases example.net, example.org, and example.us for the website example.com). This is the easiest way to do this. However, to protect such additional sites with an SSL certificate, a multi-domain SSL certificate should be installed on the main website.
Create additional domains under current webspace/subscription and point their document root to the document root of the main website (i.e. /httpdocs). It gives more flexibility in terms of website settings for every site and allows to purchase separate SSL certificate for each domain.
Set the main website as default virtual host on the IP address. Go to Tools & Settings > IP addresses > <IP Address> and select WordPress website as the default website for this IP address. In this case, it is not required to create any additional domains or aliases in Plesk - as long as other site names are resolving to the same IP address, web server will use the WordPress website as a default destination for any request that comes to this IP address. However, SSL certificate for the main website must include all domains added to your multisite network.
It is possible to mix-and-match these approaches - all of them will work together.
Warning: Plesk WordPress Toolkit extension treats multisite installations as a typical single-site deployment. Specifically:
- WordPress Toolkit will display WordPress installation, plugins, and themes on the main website of the network only.
- Plugins and themes installed via WordPress Toolkit must be “network activated” from WordPress admin dashboard.