1.1 Go Live Checklist
Copy chapter anchor to clipboard
Going Live with Parlatta HostingCopy heading anchor to clipboard
If you’re reading this chapter, you likely already have your Parlatta hosted site created, migrated, or cloned at a temporary tempurl.host URL and have it all set up the way you want it.

You’re now ready to take it live at your own domain name? Excellent! Use this go-live checklist to help you get up and running in no time!

Add your custom domain name
Update the DNS (NS or A/CNAME)
Check DNS propagation
SSL installation
Make your custom domain primary
If you get stuck at any point in this process, just start a new chat anytime with our support superheroes.

1. Add your custom domain nameCopy heading anchor to clipboard
   The first thing you’ll want to do is add your custom domain name to the Domains list in the Hosting section of your site in your Account Center.

Add a new domain to a Parlatta hosted site

The tool there provides you with an option to also add the www version of your domain if you wish. While www is no longer needed to access sites on the web, some users continue to use it. If you don’t add the www version of a site, those users won’t be able to load your site if they enter the www version in their browser.

And no worries, if you include the www version but don’t want it in the site address, just make the non-www version the Primary Domain in the last step below. Anyone who then enters your domain name in their browser with the www will be instantly redirected to the non-www address.

You’ll also see an option to Add DNS records for this domain. That option is checked by default so you can follow our recommendation to manage the DNS for your custom domain in the DNS manager of your Account Center, as seen in the 1st option of the next step below.

Add a new domain to a Parlatta hosted site

For more information about adding your custom domain name, see our Add a Permanent Domain guide.

2. Update the DNS (NS or A/CNAME)Copy heading anchor to clipboard
   Once you’ve added your custom domain name in your Account Center, you’ll want to update the DNS records for that domain. There are 2 ways you can do that:

Manage the DNS in your Account Center here at Parlatta
Manage the DNS at the domain registrar or 3rd-party DNS manager

Manage the DNS in your Account Center here at ParlattaCopy heading anchor to clipboard
For this option, all you need to do is update the nameservers at your domain registrar so they point here instead. Be sure to add the domain to your Account Center first, though, so there’s a DNS zone created for it; otherwise, changing nameservers at your registrar may fail.

Note that if you did not check the Add DNS records option when you added your custom domain in the 1st step above, you can simply click the three-dot icon to the far right of your domain name now and select Add DNS Records. That will automatically add your domain and its DNS records to the DNS manager in your Account Center.

Add DNS records for a new domain

You’ll find the Parlatta nameservers you’ll want to set at your domain registrar are shown in your Account Center DNS manager once your domain name has been added there:

ns1.wpdns.host
ns2.wpdns.host
ns3.wpdns.host

Nameservers

For more information on changing nameservers, along with a handy link list of guides from popular registrars, see our Change Your Nameservers guide.

DNS Can Be Daunting
See How to Point a Domain to Parlatta Hosting on the blog for a detailed walkthrough on updating nameservers & DNS records for a 3rd-party domain that you want to use on a Parlatta hosted site.

Manage the DNS at the domain registrar or 3rd-party DNS managerCopy heading anchor to clipboard
If you prefer to manage the DNS records of your domain at your domain registrar or in a 3rd-party DNS manager like Cloudflare, you’ll need to update the main A or CNAME record there.

The DNS info you need for your domain can be found by clicking the DNS records link in the description at the top of the screen.

Site DNS info in the Account Center

We recommend using the CNAME to point your custom domain to the tempurl.host domain of your site if possible, as that method is independent of the site’s IP address. However, many hosts do not support CNAMEs for top-level domains, so you’d use the A & AAAA records instead.

Site DNS info in the Account Center

For more information about updating DNS at your registrar, see our DNS Records guide.

If you are routing your domain through Cloudflare and managing the DNS there, please also see the Cloudflare chapter in our registrar guides for important information regarding the SSL/TLS settings there.

3. Check DNS PropagationCopy heading anchor to clipboard
   Now that you’ve updated your custom domain’s DNS records, you need to wait for those changes to propagate throughout the world so your custom domain resolves to the right place (your Parlatta hosted site) from all locations.

Don’t worry, your site will still function just fine at the tempurl.host address in the meantime.

DNS changes can sometimes take only a few minutes, but often take several hours to propagate. The time it takes is completely out of your control as it depends entirely on the registrar and communications between servers/providers.

However, you can easily check on the progress of the DNS propagation using a handy DNS lookup service like DNSChecker.org.

Nameserver changes still propagating

Once the DNS has fully propagated, you should see a green checkmark in the DNS Status column for that domain in your Account Center. If it still shows a yellow circle, click on the three-dot icon to the far right of that domain and select the Recheck DNS option to refresh the data.

Recheck DNS

For more information about DNS propagation, see our DNS Setup Tips & Troubleshooting guide.

4. SSL InstallationCopy heading anchor to clipboard
   The installation of an SSL certificate on your domain is taken care of for you automatically here at Parlatta.

A regular SSL certificate will be installed on your domain as soon as the DNS has propagated, and you’ll see a lovely green checkmark next to the domain name in your Account Center when that happens.

SSL status

However, if your site is a multisite install, you’ll likely want to generate a wildcard certificate for it, so all your subsites are also secured by the same certificate.

For more information about the types of SSL certificates we provide and how to troubleshoot any issues, see our SSL FAQs, Errors & Troubleshooting guide.

5. Make your custom domain primaryCopy heading anchor to clipboard
   Once both DNS Status and SSL Status are all green under the Domains tab for your site in your Account Center, the last step is to set your custom domain as the Primary domain for your site.

That way, regardless of which domain associated with the site is entered in a browser, your site will resolve at your custom domain name.

To get that done, all you need to do is click the three-dot icon at the far right of your custom domain name and select the Set as Primary option. Note that this option only appears once both DNS Status and SSL Status show green checkmarks.

Set a domain as primary

For more information about setting the primary domain for your site, see our Set primary domain guide.

1.2 About Free Sites
Copy chapter anchor to clipboard
Depending on your Parlatta membership plan, it may include hosting credits that can be applied toward the cost of sites hosted with us.

We do this by applying a hosting credit to your membership account that can be used to defer the per-site costs associated with whatever hosting plan you choose.

You can see more about our pricing on the Hosting Overview page. See also How Parlatta Hosting Credits Work for details on how hosting credits are applied.

1.2.1 Archiving Unused Sites
Link to chapter 2
Efficient allocation of resources is one of the ways we keep costs down for all members. Therefore, free sites will be archived after 21 days unless a permanent domain has been added to the site and set as the Primary domain, or the site’s Account Center has been visited at least once per 21 days.

Members are notified by email at least seven days before a site is archived and can prevent that from happening for another 21 days simply by clicking a link in that email. There is no limit to the number of times members can extend that 21-day period, and sites that have been archived can be reactivated within 30 days by contacting support, or see Restoring a Deleted Site below.

Note that if you have added a custom domain and set it as the Primary domain, it may still get archived if that domain’s DNS records are not resolving properly. Please review our Domains documentation for troubleshooting tips, and don’t hesitate to contact our support superheroes for help with this or any other issue you may be having.

1.3 Hosting Buyout
Copy chapter anchor to clipboard
If you wish to move your sites to Parlatta hosting but still have a contract with your existing host, we offer to buy out the rest of your existing contract with any third-party hosting company.

We do this by matching the remaining period in your contract in the form of Parlatta credit so you don’t have to pay for two hosting contracts.

For example, if you are halfway through your $200 yearly third-party hosting contract, we’ll match the remaining 6 months of hosting. This means that you will get $100 in the form of Parlatta credit. On top of that, our hosting support team will assist you throughout the migration process or even migrate the sites for you for free.

Hosting Buyout ProcessCopy heading anchor to clipboard
The hosting buyout process is as follows:

Fill in the hosting buyout form.
We will review your submission and provide you with the buyout offer if eligible.
To start the migration process, we will ask you to provide us with the details we need to migrate your sites, such as your SFTP and WordPress admin credentials.
We’ll credit your account with the amount needed for our hosting team to create your temporary domains (migration destination) and get you set up with your first month’s worth of hosting for each site.
Once you’ve checked all is good after the migration, have added your own custom domain to each site, and adjusted the domain DNS, we’ll credit your account with the sum remaining in your buyout.
FAQCopy heading anchor to clipboard
How long will it take to migrate my site?
The entire migration process usually takes 24 hours to complete. It might take longer if you have a large number of sites to migrate.

Will my site be down during the migration process?
While pointing your DNS to our servers, there may be some intermittent downtime. DNS propagation can happen instantly in certain cases, but it can also take anywhere from a few minutes to a few hours.

Will my site be fully functional after the migration?
Yes, the migration should not affect your site’s functionality in any way. As your site will be migrated to a temporary URL, you will get the chance to check the site’s functionality before adding your custom domain.

Are there any limitations on the number of sites you offer to buy out?
No, we are happy to buy out any number of sites you have.

If you have more questions related to the Hosting Buyout offer, please feel free to contact our sales team.

1.4 Creating a New Site
Copy chapter anchor to clipboard
All Parlatta members can create and manage new hosting sites in the Account Center.

DID YOU KNOW?
Parlatta members are authorized up to 10 free email accounts that can be configured in minutes to display the member’s domain in the email address. See our Email Hosting product page for details.

From the Account Center site overview screen, click the + Add Site button.

Add a new site in the Account Center

Click the Create site button under the Create new module to create a brand new site hosted with Parlatta.

hosting-create-new-site

You’ll first be prompted to select whether you want to Create a brand-new site or Create from a template.

account center create new site@2x

1.4.1 Create a Brand New Site
Link to chapter 4
If you chose to create a brand new site, your next step will be to select the hosting plan you want for your new site.

Available Parlatta hosting plans

Note that if you just signed up on a Hosting Only plan, you would not see the plan table above unless you quit the onboarding process and come back later. In that case, the hosting plan you signed up for would be locked in.

You’ll then have the option to purchase the Hourly Backups add-on right away for your new site. This add-on provides you with up to 720 automatic backups & restore points every month, which can be invaluable if you’re running an active e-commerce store. If you choose not to add this to your site at the moment, simply select the Basic option, which is free.

Please note that the Hourly Backups option is not available for selection for sites hosted on the Quantum plan. Refer to Quantum Plan Restrictions for more details.

hosting create backups add@2x

Next, input the temporary website URL you desire for your new site, and click the blue arrow button to proceed.

Create a temporary URL for a new hosted site in the Account Center

Enter your preferred admin credentials on the Create WordPress Administration Account screen and click the blue arrow button to continue.

create-wordpress-admin-account

Choose where you would like your site to be hosted. For optimal performance, choose a location that is nearest to the majority of your website visitors. For more information, refer to the Locations & Regions chapter below.

Select server location for a Parlatta hosted site

Key Points to Keep in Mind When Creating New Hosted SitesCopy heading anchor to clipboard
You can change your ‘Site Title’ at any point in the future.
Your ‘Temporary Destination Domain’ (e.g., xxxxxx.tempurl.host) CANNOT be altered in the future without using the site migration tool. This link is what you’ll use to access the site before configuring DNS and selecting a final primary domain.
Your ‘WordPress admin’ user information can be modified in the future. Remember the password you set to access the WordPress Dashboard once the site is ready. If you forget it, you can always reset your password via email.
The ‘Server’ location CANNOT be changed in the future without modifying DNS information or migrating your site. It’s a good practice to always choose the location closest to where the majority of your site’s visitors are located.
While you can convert a single site to a ‘Multisite’ network in the future, transitioning back the other way is considerably more complex.
To deter phishers and hackers, certain terms are not allowed in temp domains, including: ‘agric’, ‘securip’, ‘apple’, ‘google’, ‘gmail’, ‘netflix’, ‘paypal’, ‘amazon’, ‘billing’, ‘netfix’, ‘bill-‘, ‘-bill’, ‘credit-‘, ‘dhl’, ‘-ing’.

1.4.2 Create From a Template
Link to chapter 4
If you opted to create a new site from a template, you’ll have the opportunity to choose from one of the 27 pre-configured Parlatta templates or one of your personalized Site Templates.

All of our available pre-configured templates are listed under the Parlatta Templates tab.

hub create from template@2x 1

The Parlatta templates are designed using popular free themes and plugins sourced from the WordPress repository, in addition to our Pro plugins. Defender, Smush, Hummingbird, Forminator, Beehive, and SmartCrawl are all enabled, with settings optimized for the site. Each template also includes a default Forminator contact form.

Pro Tip
If you prefer to create sites without any of the Parlatta plugins installed (except, of course, the Parlatta Dashboard, which is necessary for all sites linked to your Account Center), you can create your own custom template configured to your preferences and use it to create new sites.

You can preview any Parlatta site template in a live preview by clicking the Preview link, which will open in a new tab. Click the Use Template button to select the template you want for your new site.

You can search for a specific Parlatta template using the Search field, sort them by recently added or alphabetical order, or filter them to display only those that catch your interest.

hub filter templates@2x

Any custom templates you have created will be found under the My Templates tab.

Create site from a template

To create a new site from one of your custom templates, simply click the Use template button. (Please note that you can’t preview your custom templates, as they are actually backups. For more details, refer to the Custom Templates FAQ.)

Regardless of whether you choose a Parlatta template or one of your custom templates, you’ll first need to select the hosting plan you want for the new site.

Available Parlatta hosting plans

If you just signed up on a Hosting Only plan, you won’t see the plan table above unless you exit the onboarding process and return later, in which case the hosting plan you signed up for will be locked in.

You’ll then have the option to immediately add the Hourly Backups add-on for your new site. This add-on provides up to 720 automatic backups & restore points each month, which can be essential if you run an active e-commerce store. If you decide not to include this at the moment, simply choose the Basic option, which is free.

Add Hourly Backups add-on when creating a Parlatta hosted site.

Next, provide the temporary URL you wish to assign to the new site.

Create a temporary URL for a new hosted site in the Account Center

Remember to review the Key Points to Keep in Mind When Creating New Hosted Sites mentioned above when creating a site from a template.

If you’ve chosen to use a Parlatta template, you’ll then input the credentials you want for the administrator account. This step isn’t necessary if you’re creating a site from one of your custom templates, as the admin user already exists in your template and will be automatically included.

Hosting-cloned-site-admin-account

Lastly, select where you want your site to be hosted. For optimal performance, choose a location that is nearest to the majority of your website visitors. For more details, refer to the Locations & Regions chapter below.

Select server location for a Parlatta hosted site

Once you’re ready, click the blue arrow to proceed and initiate the site creation process.

1.5 Migrating An Existing Site
Copy chapter anchor to clipboard
You have two options for migrating your existing site to WPMU DEV hosting: using our migration tool or requesting a manual migration from our hosting support team.

We strongly recommend using the migration tool because it simplifies and speeds up the process, automatically resolving any issues that could potentially interfere with a smooth migration.

Prepare to MigrateCopy heading anchor to clipboard
As a first step, make sure to back up your site. Do this at your original hosting provider. While it’s unlikely that the migration process will harm your site, especially when using the migration tool, backing up is always a crucial precaution when making significant changes to your site.

Regardless of the migration method you choose, you will need your current FTP (File Transfer Protocol) username and password. The migration tool connects WPMU DEV servers to your host’s servers via FTP. If you’re requesting a manual migration from our team, they will also require the same FTP credentials.

If you’re unsure about where to find the FTP credentials for your existing site, they should be accessible from your dashboard or control panel at your original hosting provider.

If you’re having trouble locating the FTP credentials at your host, refer to the “Getting FTP Credentials From Your Host” section below for guidance on some popular hosts. If you can’t find them, don’t hesitate to contact your hosting provider’s support team for assistance.

If you encounter any difficulties, feel free to start a live chat or create a support ticket, and our team will be happy to help you.

1.5.1 Migration Tool Method (Recommended)
Link to chapter 5
The WPMU DEV migration tool offers a robust server-to-server (SFTP) migration process that is more reliable than PHP-driven migrations (such as using a plugin).

Compared to PHP, the migration tool is less susceptible to timeout issues and handles all file transfers and URL redefinitions in a single smooth process. It eliminates the need for various programs or utilities that users often don’t utilize. Assuming the source server isn’t experiencing FTP-related problems, using the migration tool results in a faster and safer migration process.

Please note that this chapter provides guidance on how to automatically create a new WPMU DEV hosted site and migrate your existing third-party hosted site into it.

If you already have a WPMU DEV hosted site that you’d like to use as the destination for your migration, you can utilize the “Migrate Existing Site” option under the Hosting > Tools tab in your Account Center.

Create a New WPMU DEV Site for MigrationCopy heading anchor to clipboard
From the My Sites overview screen, click the “+ Add Site” button at the top-right to initiate the creation of a new site.

Add a new site in the Account Center

Next, select the “Migrate” option.

Migrate an existing site to WPMU DEV

A modal window will appear, prompting you to choose the site you intend to migrate. The dropdown will display a list of all sites currently connected to the Account Center. If the desired site isn’t listed, it means it’s not connected. In this case, click the “Please add it to your Hub first” link and follow the provided instructions.

Select site to migrate to WPMU DEV

Upon selecting the site, click the arrow, then choose the hosting plan for the site you’re migrating. Proceed by clicking the arrow once more.

Available WPMU DEV hosting plans

You’ll then have the opportunity to select your preferred migration method. To utilize the migration tool, opt for the (S)FTP migration option and click the arrow to proceed.

Migrate an existing site to WPMU DEV via (S)FTP

On the subsequent screen, input your desired temporary domain name in the provided field, and click the arrow to continue. This temporary domain will be used to access your new site until you configure DNS records for your eventual custom domain name. For more information on pointing a custom domain to your site, refer to our DNS documentation.

Enter temporary URL for new WPMU DEV hosted site

Next, choose the geographic region where you’d like your site to be hosted.

Select server location for new WPMU DEV hosted site

The migration tool will initiate the creation of the new hosted site, which will serve as the destination for your migration. This process typically takes only a few minutes.

hub sites add new progres@2x

Once the site is created, the screen will refresh, and a modal window will appear, requesting you to provide the (S)FTP credentials for the site you intend to migrate.

FTP manual migration form in the Account Center

If you don’t have the (S)FTP credentials for your source site, you can usually find them in that site’s dashboard or control panel at your current hosting provider. If they aren’t available, create them and enter them in the provided fields.

• Host: The (S)FTP hostname you use to access your site’s file system.
• Port: The port used by your host’s connection protocol.
• FTP Username: The username of a user with access to your site’s WordPress root.
• FTP Password: The password for the above user.
• WordPress Install Path: After WPMU DEV servers access your site, they will attempt to locate your site’s files. In most cases, this process is seamless. However, there may be instances where the path to these files includes an unknown directory that our servers cannot resolve, causing the migration to fail. If you know the FTP path to your site’s files, you can enter it here. The install path can usually be found in your site’s wp-admin under Tools > Site Health > Info > Directories and Sizes > WordPress directory location. If necessary, you can also refer to the “Getting FTP Credentials From Your Host” section below for help finding the install path at your host.
• Source Site Hosting Provider: The name of your current hosting provider (e.g., Bluehost).

Once all the required information is entered, click “Start Migration.”

Start a manual migration in the Account Center

The next screen will display the progress of the migration, including an estimate of the time remaining. Note that the duration of the migration process depends on your site’s size and your existing host’s speed.

You’re free to leave this screen while the migration is underway; we’ll notify you via email once it’s complete. If necessary, you can cancel the migration by clicking the “Cancel Migration” button.

Site migration progress in the Account Center

After a successful migration, the temporary domain you used during the migration process will automatically become the primary domain for the migrated content. This means that your migrated content can be accessed using both the original URL and the temporary domain you set up for your new WPMU DEV site.

To ensure that the migration was successful, we recommend visiting the temporary domain. You can do this by clicking the “WP Admin” option next to the temporary domain in The Hub site manager.

In the event that the migration fails for any reason and you need to access the new site hosted with WPMU DEV, you’ll need to reset the password for the auto-created admin account. This account is generated using the email address associated with your WPMU DEV account, and the default username is “admin.” To reset the password, follow these steps:

1. Go to the “/wp-login.php” screen for the new site.
2. Click the “Lost your Password?” link.
3. Enter your WPMU DEV email address.
4. Click the reset link sent to your email.
5. Set a new password for the default admin account.

If you’re satisfied with the migration and want to proceed, it’s time to add your permanent domain name and edit your DNS records. For guidance on this process, refer to our WPMU DEV DNS Records documentation.

In case you encounter any issues during the migration process, you can consult our migration troubleshooting guide for common errors and their solutions. If the problem persists, don’t hesitate to contact our support team for assistance.

1.5.2 Manual Migration by WPMU DEV Staff
Link to chapter 5
As a WPMU DEV member, you also have the option to request a manual migration of your site by our hosting support team if the automated migration tool doesn’t work for you.

If you’re concerned about downtime during migration, you can refer to our guide on “How To Manually Migrate WordPress Sites Quickly With No Hosting Downtime” to learn how our expert hosting support team can help you avoid it.

Similar to the previous chapter, this section provides a guide on how to automatically create a new WPMU DEV hosted site and submit a request for a manual migration of your third-party hosted site into it.

If you already have a WPMU DEV hosted site that you want to use as the destination for your migration, you can use the “Migrate Existing Site” option under the Hosting > Tools tab in your Hub.

Create a New WPMU DEV Site for MigrationCopy heading anchor to clipboard
From the My Sites overview screen, click the “+ Add Site” button at the top-right to initiate the creation of a new site.

Add a new site in the Hub

Next, select the “Migrate” option.

Migrate an existing site to WPMU DEV

The dropdown menu on the next screen will reveal a list of all the sites currently connected to The Hub. If the site you wish to migrate does not appear in the list, then it is not connected. Click the “Please add it to your Hub first” link and follow the provided instructions to connect the site. Once the site is connected, select it from the dropdown menu and click the arrow to proceed.

Select site to migrate to WPMU DEV

After selecting the site, click the arrow, then choose the hosting plan for the site you’re migrating. Click the arrow again to continue.

Available WPMU DEV hosting plans

You’ll then be prompted to select the migration method. To request a manual migration by our hosting support team, select the “Help me migrate my site” option and click the arrow to proceed.

Migrate an existing site by WPMU DEV staff

On the next screen, enter your preferred temporary domain name in the provided field, and click the arrow to continue. This temporary domain will serve as the access point for your new site until you configure DNS records for your eventual custom domain name. Learn more about pointing a custom domain name to your site in our DNS documentation.

Enter temporary URL for new WPMU DEV hosted site

Choose the geographic region where you want your site to be hosted.

Select server location for a WPMU DEV hosted site

The migration tool will then proceed to create the hosted site that will serve as the destination for your migration. This process typically takes only a few minutes.

New site creation progress in the Hub

Once the site is created, the screen will refresh, and a modal window will appear, requesting access credentials for the site you intend to migrate.

To request a manual migration of your site by the WPMU DEV hosting support team, follow these steps:

1. Enter the required information for accessing your source site:

• Admin URL: Enter the URL to the admin area of your site, without the protocol (http/https).
• Admin username: The username of an administrator user on that site.
• Admin password: The password for the above user. Click the “Next” button to proceed.

1. On the next screen, provide login credentials to your Hosting control panel and/or (S)FTP/SSH details. The hosting support team needs at least one of these to migrate your site. You can provide both if available. Select the appropriate option and enter the required information.
2. Enter the following Host/Server Details:

• Server/cPanel login URL: The URL needed to access the control panel for your site at your 3rd-party host.
• Source Site hosting provider: The name of your current hosting provider.
• Host/cPanel username: The username you use to log in to your site’s control panel.
• Host/cPanel password: The password for the above user.

1. Enter the FTP/SFTP/SSH Details:

• Host: The hostname you use to access your site’s file system (e.g., ftp.mysite.com).
• Port: The port used by your host’s connection protocol.
• Username: The username of a user that can access the root of the WordPress install.
• Password: The password for the above user. Optionally, provide any other information needed to access the file system of the site you want to migrate, such as the server path if you have multiple sites installed in the same directory.

1. Once you have provided all the required and optional information, click the “Submit” button to submit your request.
2. A confirmation notice will appear on the screen, indicating that your request has been successfully submitted. The notice will contain a link to the private support ticket created for you in the Hosting Support forum.
3. If the notice closes before you click on the ticket link, you can find it listed in the “My Tickets” section of the Support area in your Hub.
4. The hosting support team will be notified of your request and will proceed with the manual migration of your site within 24-48 hours. You will receive an email notification when they reply to your ticket. This email will contain a link back to your ticket, where you can reply if needed. Please note that you should reply within the ticket interface and not directly in the email itself.

By following these steps, you can initiate a manual migration of your existing site to WPMU DEV hosting with the assistance of the hosting support team.

Here are the details on supported migrations, cloning, and creating a new site in WPMU DEV hosting:

Supported Migrations & Conversions

Supported migrations:

• Single site -> Single site
• Multisite -> Multisite

Supported conversions:

• Single site -> Multisite
• Subsite -> Single site (may require cleanup and configuration adjustments)
• Multisite -> Single site (only if there’s a main site, no subsites)
• Subdomain -> Subdirectory (only if there’s a main site, no subsites)
• Subdirectory -> Subdomain (only if there’s a main site, no subsites)
• Backups made using the All-in-One Migration plugin (.wpress format) should be avoided as full extraction isn’t guaranteed.

Not supported – Out of scope:

• Single -> Subsite (requires a third-party developer)
• Subsite -> Subsite (requires a third-party developer)

Cloning a Site

The WPMU DEV cloning tool duplicates a site’s files and database to create an identical copy with a new domain. Cloning is useful for moving sites to new locations or creating templates.

Accessing the Cloning Feature

You can access the cloning feature from:

1. The “Add Site” screen.
2. The site options menu on the “My Sites” screen.

Clone an Existing Site

1. Click the “Clone from my sites” button and select the site to be cloned from the dropdown.
2. Enter a temporary domain name for the cloned site.
3. Select the desired server location.
4. Click the blue arrow to start the cloning process.

Please review the “Things to Remember When Creating New Hosted Sites” before proceeding with cloning.

Creating a New Site

Hosting Buyout:
If you want to move your sites to WPMU DEV hosting while having a contract with another host, WPMU DEV offers to buy out the rest of your existing contract by matching the remaining period in WPMU DEV credit.

Migration Process:

1. Fill in the hosting buyout form.
2. WPMU DEV will review your submission and provide a buyout offer if eligible.
3. Provide details for migration, and your account will be credited for necessary expenses.
4. After migration and verification, your account will be credited with the remaining buyout amount.

Creating a New Site:

1. From the Hub, click “+ Add Site” and choose to create a brand-new site or use a template.
2. Select a hosting plan and optional Hourly Backups add-on.
3. Enter a temporary URL for the new site.
4. Provide admin credentials and select server location.
5. Complete the process and review things to remember.

Migrating an Existing Site

Migration Tool Method (Recommended):

1. Select “Migrate” for an existing site.
2. Choose the site to migrate and a hosting plan.
3. Select the (S)FTP migration option and enter details.
4. Provide a temporary domain and server location.
5. The migration tool creates the destination site.
6. Enter source site (S)FTP credentials.
7. Monitor the migration progress and receive email notifications.

Manual Migration by WPMU DEV Staff:

1. Select “Migrate” for an existing site.
2. Choose the site to migrate and a hosting plan.
3. Select the “Help me migrate my site” option.
4. Provide temporary domain and server location.
5. Create a task with required access details.
6. Submit the request, and a private ticket is created.
7. Hosting support performs the migration and replies within 24-48 hours.

For more details, please refer to the original documentation or contact WPMU DEV support for assistance.

Clone from a Template

If you choose to clone a new site from a template, you have the option to select from pre-configured WPMU DEV templates or your own custom Site Templates.

WPMU DEV Templates

1. Navigate to the “Clone from my sites” option.
2. Click the “Clone from a template” button.
3. Choose from available WPMU DEV templates under the “WPMU DEV Templates” tab.
4. Pre-configured templates include popular free and Pro plugins, optimized settings, and a default Forminator contact form.
5. You can preview templates or click “Use Template” to select one for your new site.
6. Use filters, search, and sorting to find specific templates.
7. Custom templates you’ve created are under the “My Templates” tab.

Custom Templates

1. To clone from your custom template, click “Use template” for the desired template.
2. You won’t be able to preview custom templates as they are backups.
3. Regardless of the template choice, select the hosting plan for the new site.
4. Enter a temporary URL for the new site.
5. Review “Things to Remember When Creating New Hosted Sites.”
6. If using a WPMU DEV template, enter admin credentials; not needed for custom templates.
7. Choose the server location for best performance.
8. Click the blue arrow to initiate the site cloning process.

Important Note:
When using a template to clone a site, the new site will be created on the basic Bronze hosting plan. Keep this in mind to ensure your custom templates do not exceed the Bronze plan’s capacity (max. 15GB) to avoid site creation failures. You can upgrade the hosting plan for the new site after creation.

Migrate a Site to a New Region

If you want to migrate an existing site to a different hosting region, using the Cloning feature is the recommended method.

1. Follow the instructions in the “Clone an Existing Site” section.
2. At the “Server Location” step, select the new region for the cloned site.
3. Verify that everything works as expected on the new cloned site.
4. In the original site’s “Domains” tab, delete the domain name.
5. In the cloned site’s “Domains” tab, add the domain name.
6. Adjust the DNS settings of the domain to point to the new cloned site.
7. Once DNS and SSL check green for the new cloned site, delete the old original site.

Cost Considerations:
The cost depends on the time between creating the cloned site and deleting the original site.

Example:

• Clone on the 1st day of the original site’s billing cycle.
• You’ll incur an additional charge for the new site.
• Deleting the original site results in pro-rated credits for the remaining billing cycle.

Scenario A:

• Clone on day 5 of the original site’s billing cycle.
• Immediate deletion of the original site results in pro-rated account credits.
• The cost for the original site is minimal.

Scenario B:

• Clone on day 5 of the original site’s billing cycle.
• Delete original site on day 15.
• More pro-rated account credits than Scenario A.

Scenario C:

• Clone on day 5 of the original site’s billing cycle.
• Delete original site on day 29.
• Very small cost for the original site.

Refer to “How WPMU DEV Hosting Credits Work” for more information on hosting credits.

Troubleshooting Cloning

Analytics

If Analytics were enabled on the original site, you might see the same statistics on the cloned site. Deactivate Analytics on the cloned site, then reactivate it to get fresh and relevant stats.

Database

The cloned site’s database name will be identical to the original site’s, and it cannot be changed. This design choice ensures a smooth transfer without the complexities of renaming databases.

Each hosted site is a separate hosting instance, and the new cloned site’s database is specific to that site.

Connect a Site

The Connect module in Hub 2.0 allows you to connect sites not hosted with WPMU DEV to the Hub. For detailed information, refer to our documentation on connecting your site to the Hub.

Restoring a Deleted Site

If you want to restore a deleted WPMU DEV hosted site, follow these steps:

1. Create a new site using the same WPMU DEV account, temporary tempurl.host name, and region as the original site.
2. Go to the “Hosting > Backups” tab, and you’ll see backups of the original site available.
3. Within 30 days of deletion, restore one of the available backups to make your site live again.
4. Note: The restored site will have a new IP address. Update the A record of any custom domain pointing to the previous IP address.

Getting FTP Credentials From Your Host

This chapter provides guidance on obtaining FTP credentials from your existing 3rd-party host, which are needed for migrating your site using the migration tool in your Hub or requesting manual migration by WPMU DEV support staff.

cPanel

1. Log in to your cPanel.
2. Scroll down to the Files section and click on “FTP Accounts.”
3. If there isn’t an existing FTP user with a known password, create a new one:

• Enter a username for the FTP user.
• Enter a secure password (note it down for later use).
• Delete the auto-filled content in the Directory field to provide full access to your site’s root directory.
• Set Quota to Unlimited.
• Click “Create FTP Account.”

1. In the FTP Accounts list, find the account you created and click “Configure FTP Client.”
2. In the Manual Settings section, you’ll find the FTP information needed for migration.

For manual migration:

• Follow the instructions in the “Manual Migration by WPMU DEV Staff” chapter.

For migration using the Migration Tool:

• Use the FTP information in the Migrate Existing Site modal as follows:
• Select the appropriate protocol (SFTP or FTP).
• Enter the FTP Server as the Host.
• Set the Port according to the protocol: 21 for FTP, 22 for SFTP.
• Leave the WordPress install path blank.
• Click “Start Migration” in the modal to begin the migration process.

The migration time depends on your site’s size.

SiteGround

To get FTP credentials for your SiteGround hosted site:

1. Log in to your SiteGround account.
2. Click the “Websites” link in the main navigation.
3. Click the “Site Tools” button for the site you want to migrate.
4. In the sidebar on the next screen, click the “FTP Accounts” option from the Site menu.
5. Create a new FTP account for migration:

• Enter an Account Name (username) for the FTP user.
• Enter a secure Password for the FTP user.

1. Click the “Create” button.
2. Click the vertical ellipsis icon to manage the FTP account.
3. In the contextual menu, click “FTP Credentials” to view the FTP Settings.

For manual migration or migration using the Migration Tool in your Hub:

• Select the appropriate protocol (SFTP or FTP) based on your host’s protocol.
• The Hostname is what you would enter for the Host.
• The Port should be set according to the protocol: 21 for FTP, 22 for SFTP.
• Leave the WordPress install path blank.

WP Engine

To get SFTP credentials for your WP Engine hosted site:

1. Log in to your WP Engine account.
2. Navigate to the “Sites” screen and click on the site you want to migrate.
3. In the Production menu, click the “SFTP users” option.
4. Create a new SFTP user for migration:

• Enter a Username for the SFTP user.
• Enter a secure Password for the SFTP user.
• Be sure to select your Production environment.

1. Click the “Add SFTP user” button.
2. View the new SFTP account details.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• The SFTP Address is what you would enter for the Host.
• WP Engine uses port 2222.
• Leave the WordPress install path blank.

Once you have the FTP or SFTP credentials, you can use them for migration as described earlier. The time for migration depends on the size of the site.

Cloudways

To get SFTP credentials for your Cloudways hosted site:

1. Log in to your Cloudways account.
2. Click on the “Applications” screen (not Servers).
3. Click on the site (Application) that you want to migrate.
4. In the “Access Details” section of your Application, click the “Add” button under “Application Credentials”.
5. Create a new SFTP user for migration:

• Enter a Username for the SFTP user.
• Enter a secure Password for the SFTP user.

1. Click the “Submit” button.
2. View the new SFTP account details.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• The Public IP is what you would enter for the Host.
• Cloudways uses port 22.
• The WordPress install path should be set to /public_html.

GoDaddy Managed WordPress

To get SFTP credentials for your GoDaddy Managed WordPress hosted site:

1. Log in to your GoDaddy account.
2. On the “My Products” page, click the “Manage” button in the Managed WordPress section for the site you want to migrate.
3. On the next screen, click the “Overview” button for the site.
4. In the site Overview area, navigate to the “Settings” screen and click the “View” link in the SFTP/SSH details row.
5. View the SFTP Settings info.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• The Hostname is what you would enter for the Host.
• GoDaddy Managed WordPress uses port 22.
• Leave the WordPress install path blank.

Once you have the SFTP credentials, you can use them for migration as described earlier. The time for migration depends on the size of the site.

DreamHost Managed WordPress (DreamPress)

To get FTP credentials for your DreamHost DreamPress hosted site:

1. Log in to your DreamHost account.
2. Click the “Managed WordPress” option in the WordPress menu in the sidebar.
3. Click the “Manage” button for the site you want to migrate.
4. In the “Manage Files” section, toggle on the “Show Credentials” option to reveal the SFTP Settings info.
5. Additionally, click the “Manage Files” button to open the File Manager utility and copy the WordPress install path.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• The Host shown here is what you would enter for the Host.
• DreamHost Managed WordPress uses port 22.
• Enter the WordPress install path that you obtained from the File Manager.

Flywheel

To get SFTP credentials for your Flywheel hosted site:

1. Log in to your Flywheel account.
2. Click the “Account” option in your profile menu at the top-right of the screen.
3. You’ll see the SFTP Access info in the “SFTP Access” section.

To find the WordPress install path:

• Use the SFTP Access info in your preferred FTP Client to access your site files. The path will be displayed in the client.
• Alternatively, combine your Flywheel username with the name of your site from the Sites screen to determine the install path.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• Use “sftp.flywheelsites.com” for the Host (Flywheel uses the same hostname for all sites).
• Flywheel uses port 22.
• Enter the WordPress install path as obtained from your FTP client or calculated above.

Once you have the SFTP credentials and other information, follow the migration process as described earlier. The tool will handle the unique file structure of Flywheel hosted sites during migration.

Kinsta

To get SFTP credentials for your Kinsta hosted site:

1. Log in to your Kinsta account.
2. Navigate to the Sites screen and click on the site you want to migrate.
3. In the Info section for your Live environment, scroll down to the SFTP/SSH area to find the SFTP info.
4. Note the Path shown in the Basic details area at the top of the same screen, which indicates your WordPress install directory.

For manual migration or migration using the Migration Tool in your Hub:

• Select the SFTP option for the protocol.
• The IP address shown in your Kinsta account for the Host is what you would enter for the Host.
• The Port should match the exact port shown in your Kinsta account for your site.
• Enter the Path you noted above for the WordPress install path.

Hostinger

To get FTP credentials for your Hostinger hosted site:

1. Log in to your Hostinger account and click the Manage button for the site you want to migrate.
2. On the Hosting Account screen, scroll down to the Files section and click on FTP Accounts.
3. Create a new FTP user for your migration:

• Directory: Keep the default “/public_html” to access the root directory for your site.
• Username: Enter the username you want for this FTP user.
• Password: Enter the secure password you want to use for this FTP user.

For manual migration or migration using the Migration Tool in your Hub:

• Select the FTP option for the protocol.
• The Hostname as shown in your Hostinger account is what you would enter for the Host (remove the ftp:// part).
• Hostinger uses port 21.
• Enter “/public_html” for the WordPress install path to connect to the root directory of your WordPress site.

Once you have the SFTP or FTP credentials and other information, follow the migration process as described earlier. The time it takes to complete will depend on the size of the site you’re migrating.

Changing Regions

If you wish to migrate your site from one hosting region to another, you can use the Clone tool in the Hub for a simple migration process. Alternatively, you can request a Manual Migration by WPMU DEV Staff.

Keep in mind the following considerations when changing regions:

1. Hosted backups are regionally isolated and cannot be migrated with the site. Download any backups you want to preserve before initiating the migration.
2. Hosting backups cannot be accessed from a different region, and we cannot move them for you afterward.
3. Migrating to a new region requires the assignment of a new dedicated IP address. DNS settings, including IP address-dependent plugins or integrated apps, will need to be reconfigured.
4. There will be downtime during the migration process. The original site will cease to function once migration begins. Migration time depends on site size, and reconfiguring plugins and apps on the new site depends on admin skill.

Plans & Usage Limits

Each hosted site comes with its own plan that includes a dedicated IP, memory, CPUs, storage, and usage limits. Note that creating additional databases for your sites is not possible in Managed WordPress Hosting.

Here are some key points about our hosting plans:

• Upgrading hosting plans is possible at any time.
• Downgrading is not directly possible due to server architecture and disk sizes.
• Staging environments are hosted on the same Virtual Private Server as live sites, so upgrading won’t affect staging.
• While there are no hard limits on visits, bandwidth, or traffic, recommended visit levels are provided for each plan.
• Resource-intensive factors like WordPress Multisite, membership sites, and e-commerce sites might require higher plans.
• Poorly coded themes or plugins can impact performance and may require plan upgrades for improved results.
• Each hosting plan allows one WordPress installation, which can contain unlimited sites if converted to multisite.

Using WooCommerce:

• You’re not limited by your plan when hosting WooCommerce, but resource-intensive plugins and high traffic might require higher plans.

Virtual CPUs:

• Hosting plans offer different shared vCPUs, but performance depends on RAM and vCPUs balance.

Maximum Parallel Users:

• The maximum number of parallel users is dependent on various factors, including plugin and theme performance.

For more information, refer to our hosting comparison page and other relevant resources.

Memory Limits

Each hosting plan has specific RAM allocated to WordPress. The WP memory limits for each plan are as follows:

• Quantum: 128MB
• Bronze and Silver: 256MB
• Gold and Platinum: 512MB
• Uranium and Titanium: 756MB
• Palladium: 1024MB

Memcached Memory Limit

Memcached is a caching system that caches data in memory (RAM) to improve performance. The memcached memory limit for each hosting plan is as follows:

• Quantum: N/A (Object Cache not available)
• Bronze: 32 MB
• Silver: 128 MB
• Gold: 512 MB
• Platinum: 1024 MB
• Uranium: 1280 MB
• Titanium: 1536 MB
• Palladium: 1792 MB

PHP Workers

The number of PHP workers/max children affects PHP processes on the server. Each hosting plan offers a different number of PHP workers:

• Quantum: 3 PHP workers/max children
• Bronze: 5
• Silver: 12
• Gold: 55
• Platinum: 115
• Uranium: 205
• Titanium: 410
• Palladium: 614

Max Concurrent Connections

The maximum number of concurrent MySQL database connections for each hosting plan is as follows:

• Quantum: 25 concurrent MySQL connections
• Bronze: 50
• Silver: 150
• Gold: 300
• Platinum: 500
• Uranium: 800
• Titanium: 1000
• Palladium: 1200

InnoDB Buffer Pool Size & Instances

InnoDB buffer pool size and instances for each hosting plan:

Plan	InnoDB Buffer Pool Size	Instances
Quantum	64MB	1
Bronze	256 MB	1
Silver	512 MB	1
Gold	4096 MB	2
Platinum	8192 MB	4
Uranium	12288 MB	8
Titanium	16384 MB	12
Palladium	20480 MB	16

Maximum Execution Time

The default max_execution_time is 300 seconds for all hosting plans.

Upgrading or Downgrading Your Hosting Plan

To upgrade your hosting plan, navigate to the Hosting tab in your Hub, go to the Overview screen of your site, and click the Upgrade button in the Plan row. Choose the desired plan from the options.

Downgrading Limitations

Downgrading is not directly possible due to server architecture and disk sizes. If you need to downgrade:

1. Migrate the original site to a new site on a lower plan.
2. Create a template from the original site and use it to create a duplicate on a lower plan.
3. Create a backup, delete the site, and recreate it on a lower plan with the same tempurl address and region.

Make sure to create and download a backup of the original site first. Each option may involve a minimal additional cost. DNS settings should be managed accordingly.

Modifying Size and Type Limits

This chapter explains how to adjust the default limits for file sizes and types that can be uploaded to the media library in WordPress.

If you have any questions about file upload limits or need assistance in setting the right limits for your site, you can reach out to our hosting support Superheroes through Live chat or submit a support ticket using the Support tab in your WPMU DEV Dashboard.

WPMU DEV Max Upload File Size

The maximum file upload size for all WPMU DEV-hosted sites is 128MB, regardless of the hosting plan. Members can restrict the size of uploaded files, but the maximum size cannot be increased. If you need to reduce this limit, you can refer to our “Modifying PHP with .user.ini” documentation.

This limit is set to enhance security and prevent potential attacks that exploit large file size limits and overwhelm your server with massive post requests.

For files larger than 128MB, it’s recommended to upload them using SFTP/SSH. You can find information on how to upload large files using SFTP & SSH in our documentation. Alternatively, you can use the “Big File Uploads” plugin, which breaks large files into smaller chunks for upload.

To check the current maximum upload size for a site, go to the WordPress media uploader: Dashboard > WP Admin > Media > Add New. The upload size limit will be displayed at the bottom of the user interface.

WordPress Default File Types

Members have the option to add or remove file types from the allowed upload list based on their needs. However, it’s important to note that each added file type introduces a potential security risk to your site or network. It’s recommended to only add file types that you require.

By default, WordPress allows uploading of the following file types:

• Images: jpg, jpeg, png, gif, ico
• Documents: pdf, doc, docx, ppt, pptx, pps, ppsx, odt, xls, xlsx, psd
• Audio: mp3, m4a, ogg, wav
• Video: mp4, m4v, mov, wmv, avi, mpg, ogv, 3gp, 3g2

Multisite Upload Limits

For multisite administrators, you can adjust both file size and file type limits in the Network Settings: Dashboard > Network Admin > Settings > Network Settings.

Scroll down to the Upload Settings section, where you’ll find the Upload file type and Max Upload File Size fields.

Adding/Removing File Types in Multisite

In the Upload file types field, you can add the file extensions of the desired types, separating them with a single space. You can also remove extensions of file types you don’t want to allow.

Modifying the File Size Upload Limit in Multisite

In the Max Upload File Size field, enter a size in kilobytes, up to 12800KB (128MB), to set the maximum file size for uploads to the network. The new limit will apply to all sites within the network.

Standard Installation Upload Limits

If you encounter the “Sorry, this file type is not permitted for security reasons” error message, you’ve tried to upload a file type not on your site’s allowed list or that has failed a WordPress security validation test.

Adding/Removing File Types in Standard Installations

You can add allowed file types using a plugin or a code snippet. There are plugins available on WordPress.org, such as “File Upload Types,” that allow you to easily manage allowed file types.

Alternatively, you can use a code method to add custom file types. A sample code snippet is provided, allowing you to add specific file extensions to your site’s allowed list.

If you need assistance with the correct format for adding a mime type, you can refer to a list of common mime types and extensions provided in the documentation.

Standard Installation Upload File Size

This chapter demonstrates how to increase the maximum upload file size using the “Increase Maximum Upload File Size” plugin.

Once you have installed and activated the “Increase Maximum Upload File Size” plugin, a new option called “Increase Maximum Upload File Size” will appear in your Admin Menu. Click on this link to open the plugin.

The plugin interface features a dropdown menu. When you access the UI for the first time, it will display your current maximum upload file size.

Click the dropdown menu to reveal various upload size limit options. Please note that setting a file size larger than 128MB will not override the 128MB maximum upload limit set by WPMU DEV Managed Hosting. Select your desired upload limit from the menu and then click “Save Changes.”

Once you have set a limit, the plugin will display both the default WPMU DEV Managed Hosting limit of 128MB and the lower limit established by the plugin.

WPMU DEV Server Error Pages

Sites hosted by WPMU DEV feature white-labeled error pages that are displayed when there’s a server-side issue with your site. The available error pages are as follows:

Client error pages:

• 401.html: Displayed if the site has password protection enabled and the HTTP Auth form is dismissed by the user. Note that if a user has a popup blocker enabled in their browser, the HTTP Auth form might not appear, and they would need to disable the extension for that site.

• 402.html: Displayed if the site is suspended due to required payment on your account.

• 403.html: Displayed if a connection is forbidden, possibly due to a Web Application Firewall (WAF) rule.

• 404.html: Displayed when the URL or page requested by the user cannot be found.

• 410.html: Displayed if the requested page has been deleted permanently.

• 429.html: Displayed to a user/IP if they’re attacking /wp-login.php or /xmlrpc.php (Refer to our “Bruteforce Attack Protection” documentation for details).

Server error pages:

• 500.html: Displayed if there is an internal server error.

• 502.html: Displayed if your server gets an invalid response from another web server.

• 503.html: Displayed if the server is currently unable to handle your request due to scheduled maintenance or a temporary overload.

• 504.html: Displayed if the server timed out handling your request due to a temporary overload or a long-running script.

Customizing Error Pages

You have the option to customize the server error pages with your brand or any desired custom information. For instance, if you want to personalize the default error 500 page:

Default WPMU DEV error 500 page:

You can create a customized error page that better matches your brand:

Customized error 500 page example:

This allows you to enhance your site’s branding and provide a more tailored experience to your users even when they encounter errors.

How to Customize Error Pages

To create a custom error page for any of the errors mentioned above, follow these steps:

1. Create a .html file with the error number as the filename (e.g., 500.html).
2. Add any custom HTML content you desire to this file.
3. Upload the file to the root directory of your WordPress installation.

For instance, if you want to create a custom error page for the “500 internal server error,” create a file called “500.html.”

You can use the “Manage Files” utility from your Hub’s “Tools” screen to create and add content to the file. Alternatively, you can edit the file on your computer and then upload it using the File Manager or an FTP client.

Here’s an example of the basic HTML structure for a custom error page:

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <title>Title of Your Custom Error Page</title>

<style>
/* Add your page CSS here */
</style>

<!-- If you're including jQuery in your page code, add it here -->
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script>
<script type="text/javascript">
// Custom functions here
</script>

</head>

<body>

<!-- All your page content goes here. Be sure it's properly formatted HTML, and add any needed CSS and/or JS above. -->

</body>
</html>

Your custom error pages can be as simple or creative as you like, and you can brand them according to your needs. If you’re seeking inspiration, you can check out these pages for great examples:

• 500 Error Page Templates
• 404 Page Templates

More Whitelabeling Options

WPMU DEV offers White Label services that enable you to remove all WPMU DEV branding, allowing you to use your own branding or even your client’s branding. This feature is primarily available through the WPMU DEV Dashboard Plugin. For guidance on rebranding using the WPMU DEV Dashboard Plugin, refer to our “White Label Plugins” documentation.

Additionally, the process of white labeling your site is closely linked to our “Branda” plugin. Branda simplifies white label branding, maintenance, and more. To learn more about the capabilities of the Branda plugin, explore our WPMU DEV documents on Branda.

If you’re utilizing our “Hub Client” plugin to offer the site management tools of our Hub to your clients, be sure to review the Hub Client documentation as well.

System Information

As a WPMU DEV member, you can access detailed information, including the system information, by navigating to “Support” > “System Information” in the WPMU DEV Dashboard installed on your sites.

Database:
The databases of all sites hosted by WPMU DEV run on MariaDB based on MySQL 7/8.

WordPress Multisite

Unlike many other hosts, we fully support both subdirectory (e.g., yoursite.tld/subsite) and subdomain (e.g., subsite.yoursite.tld) multisite configurations on all our hosting plans, with the exception of the Quantum plan, which is not suitable for multisite installations. Enabling multisite for a WPMU DEV hosted site is a simple process accessible through the Tools tab of your site in your Hub. For detailed instructions, refer to the “Multisite” chapter in our Hub > Tools documentation.

We also offer free Wildcard SSL Certificates for your multisite setup. However, if you prefer, you can provide your own Custom SSL Certificates.

Mapping custom domains to subsites in your multisite network is also straightforward and involves a 3-step process. If you need guidance on domain mapping, consult our “Multisite Domain Mapping” guide for step-by-step instructions.

It’s important to note that WordPress Multisite networks generally require more server resources, CPU, and memory compared to standard WordPress single installs. If your multisite network consists of numerous subsites, you may find that a higher hosting plan is necessary to meet your network’s demands.

Why Subdomains Are Discouraged

In Multisite installations, there are two primary configurations: subdirectory (e.g., mysite.com/sitename) and subdomain (e.g., sitename.mysite.com). While both options are available, we strongly recommend opting for a subdirectory install whenever possible due to several performance, SEO, and technical reasons:

1. SEO Considerations: Most SEO experts recommend subdirectories to maximize content and domain authority for your site. Subdomains are often treated as separate websites by search engines, potentially affecting SEO efforts.
2. Traffic and Performance: Subdomains tend to attract higher bot and crawler traffic, which can strain server resources and decrease performance. Each subdomain is seen as a distinct site by bots, leading to simultaneous crawling of multiple subdomains.
3. Security and DDOS Mitigation: Subdomains can complicate the prevention and mitigation of Distributed Denial of Service (DDOS) attacks.

Getting .htaccess Support

Our servers are powered by NGINX, a high-performance and stable web server, and NGINX does not support the use of .htaccess files. However, you need not worry about .htaccess functionality, as our servers automatically handle the tasks commonly associated with it.

While .htaccess files can slow down server processing due to the AllowOverride directive in Apache servers, our NGINX servers process requests more efficiently.

Common functions that are automatically managed without .htaccess on our servers include:

• Permalinks: Our servers automatically handle permalinks for you.
• Caching: Server-side caching is managed automatically, eliminating the need for plugins or manual .htaccess modifications.
• Redirects/Rewrites: Redirects can be implemented using plugins or custom server-side redirects set up by our support team.
• Security: Security measures that typically involve modifying the .htaccess file are already implemented at the server level in WPMU DEV hosting.

For any tasks you may have been achieving through .htaccess, consider reaching out to our support Superheroes. They can assist you in finding alternative approaches that don’t involve creating or modifying .htaccess files.

Getting nginx.conf Support

While our server system relies on Nginx and doesn’t support .htaccess files, there might be times when you need custom rules for specific plugin functions. Since you don’t have root access to the server, you can’t make these changes yourself.

Here’s how you can get the support you need:

1. Contact Support: Reach out to our support team via live chat or by submitting a ticket through your WPMU Dev Dashboard.
2. Explain Your Needs: Clearly describe the custom rules you require for your server configuration.
3. Superhero Assistance: Our support team will review your request and implement the necessary changes in the nginx.conf file if feasible.
4. Create a Support Ticket: You can initiate a support ticket by going to WPMU DEV DASHBOARD > SUPPORT > NEW TICKET.

Following these steps will help you get the custom server configurations you need for your site’s functionality.