Developed exclusively for WordPress sites, our managed hosting solution provides dedicated memory and storage space in highly configured Virtual Private Servers for each site hosted.

If you are not using WPMU DEV hosting, learn more about pricing, what’s included, and how to get started free.

Not sure if WPMU DEV Managed WordPress hosting is right for you?

Want to compare how to set up and self-manage a VPS hosting environment yourself? Check out Optimized WordPress Hosting: DIY or Managed? on our blog.

1.1 Go Live Checklist

Copy chapter anchor to clipboard

Going Live with WPMU DEV Hosting

If you’re reading this chapter, you likely already have your WPMU DEV 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!

  1. Add your custom domain name
  2. Update the DNS (NS or A/CNAME)
  3. Check DNS propagation
  4. SSL installation
  5. 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 name

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 Hub.

Add a new domain to a hosting 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 no www version of a site exists, it is possible they won’t be able to find your site.

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. Check that option if you want to manage the DNS for your custom domain in the DNS manager of your Hub, as seen in the 1st option of the next step below.

Add a domain

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

2. Update the DNS (NS or A/CNAME)

Once you’ve added your custom domain name in your Hub, you’ll want to update the DNS records for that domain. There are 2 ways you can do that:

Manage the DNS in your Hub here at WPMU DEV
Manage the DNS at the domain registrar or 3rd-party DNS manager

Manage the DNS in your Hub here at WPMU DEV

For this option, all you need to do is update the nameservers at your domain registrar so they point here instead.

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 Hub.

Add DNS record

You’ll find the WPMU DEV nameservers you’ll want to set at your domain registrar are shown in your Hub 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.

Manage the DNS at the domain registrar or 3rd-party DNS manager

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 at the bottom of the Domains tab in the Hosting section of your site in your Hub.

DNS module

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.

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

3. Check DNS Propagation

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 WPMU DEV 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 Hub. 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 Installation

The installation of an SSL certificate on your domain is taken care of for you automatically here at WPMU DEV.

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 Hub 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 primary

Once both DNS Status and SSL Status are all green under the Domains tab for your site in your Hub, 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 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 WPMU DEV 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 WPMU DEV Hosting Credits Work for details on how hosting credits are applied.

NOTE: Archiving Unused Sites

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, and the site’s Hub has been visited at least once. 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.

1.3 Creating a New Site

Copy chapter anchor to clipboard

All members, including those on an introductory free trial, whose sites are hosted by WPMU DEV can create and manage new hosting sites in from The Hub.

DID YOU KNOW?

WPMU DEV 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 Hub 2.0 site overview screen, click the Add a website (+) icon.

hosting-add-a-website

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

hosting-create-new-site

Choose your temporary destination and click the blue arrow button to continue.

hosting-temporary-website-url

Enter your desired 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 hosted. For best performance, select a location closest to the majority of your visitors. See the Locations & Regions chapter below for more info.

create-site-server-location

Important Information:

  • Your ‘Site Title’ can be changed at any time in the future.
  • Your ‘Temporary Destination Domain’ CANNOT be changed in the future without using the site migration tool. This is the link you will use to access the site before you configure DNS and choose a final primary domain.
  • Your ‘WordPress admin’ user information can be changed in the future. Do remember the password you set in order to access the WordPress Dashboard once the site is ready. If you lose it, you can always do a password reset by email.
  • The ‘Server’ location CANNOT be changed in the future without changing DNS information or migrating your site. The best idea is to always choose the location closest to where the majority of your site’s visitors are located.
  • You can convert a single site to a ‘Multisite’ network in the future, but it is much more challenging to go the other way.
  • To prevent phishers/hackers, we do not allow the following to be part of temp domains: ‘agric’, ‘securip’, ‘apple’, ‘google’, ‘gmail’, ‘netflix’, ‘paypal’, ‘amazon’, ‘billing’, ‘netfix’, ‘bill-‘, ‘-bill’, ‘credit-‘

1.4 Migrating An Existing Site

Copy chapter anchor to clipboard

Sites can be migrated to WPMU DEV hosting using our migration tool or by manually transferring files using sFTP/SSH and phpMyAdmin. We recommend using the migration tool because it simplifies and accelerates the process and automatically resolves issues that occasionally interfere with a smooth migration.

If you run into any trouble, just start a live chat or create a support ticket, and our team will help get your site moved. See Manual Migration by WPMU DEV Staff below for more info on that.

IMPORTANT

When migrating a site that has tracking codes like Adsense, you may want to temporarily remove those codes from the duplicate site created here to avoid any possible tracking errors or penalties due to duplicate codes on different domains. Once you’ve got everything set up on the new site here and have adjusted DNS for the domain name, you can add those tracking codes back on your new site created here.

1.4.2 Manual Migration by WPMU DEV Staff

Link to chapter 4

As a WPMU DEV member, you can also request that we manually migrate your site in case the above options don’t work for you. We can migrate either directly from the server where your existing site is currently hosted, or by using a full and complete backup of your existing site that you provide.

To get your migration done by our staff, you’d need to provide the following required information for either method to our live chat support superheroes.

They will then create the needed support ticket for you, and our hosting support techs will get the migration done. You’ll be notified in your support ticket once the migration is finished.

Info required for manual migration

From server

  1. Admin login credentials to your existing WordPress site (if Multisite please provide Super Admin details):
    • Admin Username
    • Admin Password
    • Login URL
  2. FTP credentials to your existing WordPress site:
    • Hostname
    • Username
    • Password
    • Port
    • Key-File (and password) if needed
  3. Server admin credentials to your existing WordPress site (cPanel, Plesk or equivalent at your current host):
    • Username
    • Password
    • Login URL
  4. Destination Environment
    • WPMU DEV Hosting temporary *.tempurl.host URL (can be an existing WPMU DEV hosted site you wish to overwrite, or a brand new one you create before requesting the migration)

From backup

  1. A full backup of your existing WordPress site (.zip, .tar.gz etc)
    • Must include all site files and export of your database (.sql file)
  2. Destination Environment
    • WPMU DEV Hosting temporary *.tempurl.host URL (can be an existing WPMU DEV hosted site you wish to overwrite, or a brand new one you create before requesting the migration)

Supported Migrations & Conversions

It’s important to note that some types of migrations are out-of-scope and cannot be handled by our support or hosting staff. Following are the types of manual migrations/conversions that we can and cannot do for you.

  1. Supported migrations
    • Yes – If Single site -> Single site
    • Yes – If Multisite -> Multisite
  2. Supported conversions
    • Yes – If Single site -> Multisite
    • Yes – If Subsite -> Single site (you should expect to need to perform some cleanup in the converted site, and there may be configuration issues for some plugins due to conversion)
    • Depends – If Multisite -> Single site (supported only if there’s just a main site, without subsites)
    • Depends – If Subdomain -> Subdirectory (supported only if there’s just a main site, without subsites)
    • Depends – If Subdirectory -> Subdomain (supported only if there’s just a main site, without subsites)
  3. Not supported – Out of scope
    • No – If Single -> Subsite (3rd party developer required for this type of migration)
    • No – If Subsite -> Subsite (3rd party developer required for this type of migration)

1.4.3 Getting FTP Credentials From Your Host

Link to chapter 4

This chapter provides guidance on how to get or create the FTP credentials from your existing 3rd-party host. These credentials are needed so you can proceed with the migration tool in your Hub, or with a request for manual migration by WPMU DEV support staff.

Guidance is provided for some of the more popular hosts & hosting interfaces below. If you don’t see your host listed here, check some of the existing ones to see if they can help, or start a chat with our support superheroes for assistance.

cPanel

Follow this guide to get FTP credentials for any host that uses the popular cPanel interface.

Once logged into your cPanel, scroll down to the Files section, and click on FTP Accounts.

Accessing FTP accounts in cPanel

If there is not already an FTP user available for which you know the password, you can simply create a new one for your migration.

Creating a new FTP account in cPanel

  • Log In – Enter the username you want for this FTP user
  • Password – Enter the secure password you want to use for this FTP user. You’ll want to take note of your chosen password for later use as it will not be displayed once the account is created.
  • Directory – IMPORTANT: Be sure to delete what the system adds in this field so the new user has full access to your site’s root directory.
  • Quota – Should be set to Unlimited.

Once you’ve entered all the information as above, click the Create FTP Account button.

You’ll then see the new FTP account you just created in the FTP Accounts list just beneath the form you just submitted.

Click the Configure FTP Client link for the account you just created to pop open the Manual Settings section where you’ll see the info you need.

New FTP account created in cPanel

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP or FTP option for the protocol according to the protocol used by your host.
  • The FTP Server shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: 21 for plain FTP, 22 for secure SFTP.
  • Leave the WordPress install path blank (this is why you ensured the Directory was blank when you created the FTP account as above).

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

SiteGround

Follow this guide to get FTP credentials for your SiteGround hosted site.

Once logged into your SiteGround account, click the Websites link in the main navigation. Then click the Site Tools button for the site you want to migrate.

Accessing FTP accounts at Siteground

In the sidebar on the next screen, click the FTP Accounts option from the Site menu. If there is not already an FTP user available there for which you know the password, you can simply create a new one for your migration.

Creating a new FTP account at Siteground

  • Account Name – Enter the username you want for this FTP user
  • Password – Enter the secure password you want to use for this FTP user. You’ll want to take note of your chosen password for later use as it will not be displayed once the account is created.

Once you’ve entered the information as above, click the Create button.

You’ll then see the new FTP account you just created in the Manage FTP Accounts list just beneath the form you just submitted.

Click the vertical ellipsis icon to pop open management options for the FTP account.

Accessing FTP account options at Siteground

In the contextual menu that slides open at the bottom of the screen, click the FTP Credentials option.

FTP account options at Siteground

That will pop open a little modal window with the FTP Settings info you need.

FTP account credentials at Siteground

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP or FTP option for the protocol according to the protocol used by your host.
  • The Hostname shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: 21 for plain FTP, 22 for secure SFTP.
  • Leave the WordPress install path blank so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

WP Engine

Follow this guide to get SFTP credentials for your WP Engine hosted site.

Once logged into your WP Engine account, navigate to the Sites screen and click on the name of the site you want to migrate.

Accessing FTP accounts at WP Engine

Next, in the Production menu, click the SFTP users option.

Accessing FTP accounts at WP Engine

If there is not already an SFTP user available there for which you know the password, you can simply create a new one for your migration. In the SFTP users section, click the Create SFTP user button.

Creating a new FTP account at WP Engine

That will pop open a modal window with the new SFTP user creation form.

Creating a new FTP account at WP Engine

  • Username – Enter the username you want for this SFTP user
  • Password – Enter the secure password you want to use for this SFTP user. You’ll want to take note of your chosen password for later use as it will not be displayed once the account is created.
  • Path (optional) – Leave this blank.
  • Environment – Be sure to select your Production environment to migrate your actual site.

Once you’ve entered the information as above, click the Add SFTP user button.

You’ll then see the new FTP account you just created in the area beneath the Create SFTP user section where all the info you need is displayed.

New FTP account created at WP Engine

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP option for the protocol.
  • The SFTP Address shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: Wp Engine uses port 2222.
  • Leave the WordPress install path blank so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

Cloudways

Follow this guide to get SFTP credentials for your Cloudways hosted site.

Once logged into your Cloudways account, be sure you are viewing the Applications screen, not the Servers screen. You do not want to use an SFTP user for your entire server, as using such a user would migrate everything on the server to WPMU DEV. You only want to migrate one site.

On the Applications screen, click on the site (Application) that you want to migrate.

Accessing FTP accounts at Cloudways

If there is not already an SFTP user available for that site for which you know the password, you can simply create a new one for your migration.

In the Access Details section of your Application, click the Add button under Application Credentials.

Creating a new FTP account at Cloudways

That will pop open a modal window with the new SFTP user creation form.

Creating a new FTP account at Cloudways

  • Username – Enter the username you want for this SFTP user
  • Password – Enter the secure password you want to use for this SFTP user.

Once you’ve entered the information as above, click the Submit button.

You’ll then see the new SFTP account you just created in the Application Credentials area where all the info you need is displayed.

New FTP account created at Cloudways

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP option for the protocol.
  • The Public IP shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: Cloudways uses port 22.
  • The WordPress install path should be set to /public_html so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

GoDaddy Managed WordPress

If you have any hosting plan at GoDaddy that grants you access to cPanel, follow the cPanel guide above instead.

Follow this guide to get SFTP credentials for your site hosted by GoDaddy Managed WordPress.

Once logged into your GoDaddy account, be sure you’re on the My Products page, and click the Manage button in the Managed WordPress section for the site you want to migrate.

Accessing FTP accounts at GoDaddy

On the next screen, click the Overview button for the site.

Accessing FTP accounts at GoDaddy

In the site Overview area, navigate to the Settings screen and click the View link in the SFTP/SSH details row.

Accessing FTP accounts at GoDaddy

That will pop open a modal window with the SFTP Settings info you need.

Accessing FTP accounts at GoDaddy

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP option for the protocol.
  • The Hostname shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: GoDaddy Managed WordPress uses port 22.
  • Leave the WordPress install path blank so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

DreamHost Managed WordPress (DreamPress)

Follow this guide to get FTP credentials for your DreamHost DreamPress hosted site.

Once logged into your DreamHost account, click the Managed WordPress option in the WordPress menu in the sidebar. Then click the Manage button for the site you want to migrate.

Accessing FTP accounts at DreamHost

On the next screen, scroll down to the Manage Files section and toggle on the Show Credentials option. That will reveal the SFTP Settings info you need.

Accessing FTP accounts at DreamHost

Unfortunately, it appears DreamHost does not display your WordPress install path anywhere in the control panel. So you’ll also want to click on the Manage Files button there to pop open their File Manager utility where you can get that info.

Once in the File Manager, be sure to navigate to the correct directory where your WordPress site is installed; it’s the directory that contains the wp-admin folder. Then copy the path that is displayed at the top of that screen.

Finding WordPress install path at DreamHost

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP option for the protocol.
  • The Host shown here is what you would enter for the Host.
  • The Port should be set according to the protocol used by your host: DreamHost Managed WordPress uses port 22.
  • Enter the WordPress install path that you copied above so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

Flywheel

Follow this guide to get SFTP credentials for your Flywheel hosted site.

Once logged into your Flywheel account, click the Account option in your profile menu at the top-right of the screen.

Accessing FTP accounts at Flywheel

You’ll then see the SFTP info you need displayed in the SFTP Access section on that screen.

Accessing FTP accounts at Flywheel

Unfortunately, it appears Flywheel does not display the WordPress install path for your site anywhere in their control panel. There are 2 ways to get that needed info though:

  1. Use the SFTP Access info as above in your preferred FTP Client to access your site files. Once you have navigated into the directory where your WordPress site is installed, you’ll see the install path displayed in the client. For example, this is what you might see in Filezilla where the path is indicated at the top where it says Remote Site:

    Finding WordPress install path at Flywheel

  2. Alternatively, you can know what the install path is simply by combining your Flywheel username with the name of your site as it appears on the Sites screen. For example, if your username is pcwriter and your site name is fwtest1, then the install path would be: /pcwriter/fwtest1

    Finding WordPress install path at Flywheel

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the SFTP option for the protocol.
  • Flywheel uses the same hostname for all sites, so enter sftp.flywheelsites.com for the Host.
  • The Port should be set according to the protocol used by your host: Flywheel uses port 22.
  • Enter the WordPress install path as above so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

If you have already SFTP’d into your site’s files, you may have noticed that the file structure of Flywheel hosted sites is rather unique in that the wp-admin folder, and many root files, appear to be missing. Our smart migration tool will detect that the site is hosted at Flywheel and will migrate the wp-content directory and the database, then install all missing files/folders from wordpress.org so your site will function as it should.

Kinsta

Follow this guide to get SFTP credentials for your Kinsta hosted site.

Kinsta automatically creates an SFTP account for each domain you add to your hosting plan.

Once logged into your Kinsta account, navigate to the Sites screen, and click on the site you want to migrate.

Accessing FTP accounts at Kinsta

On the next screen, in the Info section for your Live environment, scroll down to the SFTP/SSH area where you’ll find the SFTP info you need.

Accessing FTP accounts at Kinsta

You’ll also want to take note of the Path shown in the Basic details area at the top of this same screen. This indicates the directory in which your WordPress site is installed.

Finding WordPress install path at Kinsta

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • 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 be set according to the protocol used by your host. Kinsta assigns different ports for different users, so it is important to copy the exact port shown in your account for your site.
  • Enter the Path you copied above for the WordPress install path so the tool can connect to your WordPress root.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

Hostinger

Follow this guide to get FTP credentials for your Hostinger hosted site.

Once logged into your Hostinger account, click the Manage button for the site you want to migrate.

Accessing FTP accounts at Hostinger

On the Hosting Account screen, scroll down to the Files section, and click on FTP Accounts.

Accessing FTP accounts at Hostinger

If there is not already an FTP user available for which you know the password, you can simply create a new one for your migration.

Creating a new FTP account at Hostinger

  • Directory – This should be kept at the default so this FTP account can access the root directory for this site: /public_html
  • Username – Enter the username you want for this FTP user.
  • Password – Enter the secure password you want to use for this FTP user. You’ll want to take note of your chosen password for later use as it will not be displayed once the account is created.

Once you’ve entered all the information as above, click the Create button.

You’ll then see the new FTP account you just created in the List of Active FTP Accounts section just beneath the form you just submitted.

New FTP account created at Hostinger

If you are requesting a manual migration, you would provide the needed info as described in the Manual Migration by WPMU DEV Staff chapter above.

If you are migrating your site using the Migration Tool in your Hub, enter the FTP information in the Migrate Existing Site modal window as follows:

  • Select the FTP option for the protocol.
  • The Hostname as shown here is what you would enter for the Host (be sure to remove the ftp:// part if you right-click and copy the link from that screen).
  • The Port should be set according to the protocol used by your host: Hostinger uses port 21.
  • Enter /public_html for the WordPress install path so the tool can connect to the root directory of your WordPress site.

Adding FTP credentials to Hub migration tool

Once all the FTP information has been added in the Migrate Existing Site modal, click the Start Migration button. The time it takes to complete will depend on the size of the site you’re migrating.

The Connect module on the Hub 2.0 Getting started screen is used to Connect sites not hosted with WPMU DEV in The Hub. For more information, visit our full documentation on connecting your site to the Hub.

The Clone a site module in the hosting getting started wizard allows you to quickly set up new websites with your favorite plugins, theme, and configuration options from a template.

Click the Clone Site button and follow the clone module guide to make a copy of an existing site or use one of our pre-configured templates.

For guided information on using Clone to set up and use templates on your WPMU DEV hosting account, visit the Cloning Sites documentation.

1.7 Locations & Regions

Copy chapter anchor to clipboard

Members are free to choose the region in which their data is stored. We are currently partnered with DigitalOcean and Linode, and maintain regional hosting facilities in the following locations:

  • Australia (Sydney)
  • Canada (Toronto)
  • Germany (Frankfurt)
  • India (Bangalore)
  • Japan (Tokyo)
  • Netherlands (Amsterdam)
  • Singapore
  • United Kingdom (London)
  • USA East (New York City)
  • USA West (San Francisco)
How Much Does Server Location Matter?

At WPMU DEV, we’re always looking for ways that we can provide the best opportunity for a blazing-fast site, which means setting up data centers in strategic locations. In this case, we decided to test out just how much the addition of the data center in Australia impacted load times for an audience there. Check out our blog, Timed & Tested: Shave Seconds Off Your Load Time to read more about the results.

Changing Regions

The easiest way to migrate a site from one hosting region to another is by using our Clone tool in the Hub. For details on how to do that, please see the Migrate a Site to a New Region chapter in the Cloning Sites documentation. You can also request a Manual Migration by WPMU DEV Staff as detailed above.

Members are free to migrate sites from one region to another at any time but should be aware that our hosted backups are regionally isolated and cannot be migrated with the site. Members should download any hosted backups they wish to preserve before initiating the migration. Hosting backups cannot be accessed from a different region, and we cannot move them for you after the fact.

Also, migrating a site to a new region will require the assignment of a new dedicated IP address, so all DNS settings will have to be reconfigured, including any IP address-dependent plugins or integrated apps.

Finally, there is downtime to consider. The original site will cease to function the moment the migration begins. The time required for the migration depends on the size of the site or sites being moved, and once the site is up in its new region, how long it takes to reconfigure its plugins and apps depends largely on the skill of the admins.

1.8 Plans & Usage Limits

Copy chapter anchor to clipboard

Each site that we host gets its own plan, complete with its own dedicated IP, memory, CPUs, storage, and usage limits.

Each site also comes with its own database of course, but in our Managed WordPress Hosting, it is not possible to create additional databases for your sites.

See all plans and specs here.

WPMU DEV vs. Other Hosting Services

Curious about how our hosting holds up against other popular hosting services on the market? Well, even if you weren’t curious, we definitely were! So, we decided to put them all to the test and thought we’d clue you in on exactly how we did that – full transparency. Check out How to Accurately Test Your WordPress Host for more information on the tests we conducted and what online resources we used.

You can upgrade plans at any time. You can also downgrade a plan at any time. However, please note that downgrading more than one level may require a DNS change that only our support team can accomplish manually. This is because of technical limitations around storage space in the environment. In these cases, we’ll set up a new hosting environment at the desired plan and manually migrate the site’s files and content over.

Note that the staging environment of your site (if you have that set up), is hosted on the same Virtual Private Server as the live site. So when upgrading or downgrading your site, you will not lose your staging environment.

We do not set hard limits on visits, bandwidth, or traffic, but we do provide recommended visit levels for each plan to help you determine which plan will be right for you. Your site will have lower performance, including brief outages, when your memory and CPU resources are maxed out.

Factors that might use more resources and thus require you to upgrade:

  • WordPress Multisite – Multisite networks are more taxing on server resources, especially Subdomain installs and those Multisite where you will have many logged-in users.
  • Membership Sites – Membership sites receive a higher percentage of traffic where users are logged in, which means that caching systems in place are not as helpful in managing their load.
  • e-Commerce Sites – Similar to Membership sites, increased logged-in activity for checkout can cause a higher server load.
  • Poorly coded themes or plugins – Some themes and plugins just aren’t as efficient for performance as others. They may also add features that require higher processing loads.
NOTE

If a theme or plugin is so poorly coded that it slows your site to a crawl, or is throwing fatal errors, upgrading your plan would likely not improve performance until those issues are investigated and resolved.

You will notice that each hosting plan offers a different number of shared vCPUs. These virtual CPU cores play a key role in determining your site’s performance. However, it is important to note that performance is controlled by more than just the number of vCPUs and simply having more vCPUs will not necessarily improve your performance. Your site will also be heavily affected by the dedicated RAM and so the balance between RAM and vCPUs is worth noting. All of our hosting plans have been allocated specific RAM and vCPUs with that ratio in mind.

Your site’s performance can be impacted by the number of PHP workers, as these processes are responsible for running PHP on the server. Each hosting plan offers a different number of PHP workers as follows:

  • Bronze – 5 PHP workers
  • Silver – 12
  • Gold – 55
  • Platinum – 115

In addition to a specified number of PHP workers, performance can be impacted by the number of concurrent MySQL database connections available to your site. The maximum concurrent MySQL database connections for each hosting plan is as follows:

  • Bronze – 50 concurrent MySQL connections
  • Silver – 150
  • Gold – 300
  • Platinum – 500
NOTE

If a theme or plugin is so poorly coded that it slows your site to a crawl, or is throwing fatal errors, upgrading your plan would likely not improve performance until those issues are investigated and resolved.

1.8.1 Bulk Hosting Discounts

Link to chapter 8

Are there discount rates available for bulk hosting with WPMU DEV dedicated managed WordPress hosting? Yes, WPMU DEV has discount rates available for agencies or users with 20+ websites.

To learn more about bulk pricing, contact support, or start a live chat to discuss discount options.

Hosting Discounts Rates:

  • Are for users with more than 20 sites
  • Are based on volume (the more sites you have on your account, the better the rate we can offer.)

1.9 WordPress Multisite

Copy chapter anchor to clipboard

Unlike many hosts, we support (and encourage!) the use of WordPress Multisite on all plans.

However, you should be aware that WordPress Multisite networks will use more server, CPU, and memory resources than standard WordPress single installs. So, if you have more than a handful of sites, you might find you need one of the higher plans to meet your WordPress Multisite network’s needs.

Subdirectory installations (i.e., mysite.com/sitename) can be created by you in your Hosting Hub.

Subdomain installations (i.e., sitename.mysite.com) require manual work from our support team. Before converting or migrating a WordPress Multisite subdomain install, we need to be sure that you are able to:

  1. Configure wildcard DNS for the desired domain with your domain registrar
  2. Provide us with a wildcard SSL certificate for the desired name.

Please contact support to start the process for a subdomain install.

1.10 Modifying Size and Type Limits

Copy chapter anchor to clipboard

This guide covers how to safely modify the WordPress default limits on the size and type of files that can be uploaded to the media library.

After reading this guide, if you still have questions regarding file upload limits or you need help setting the right limits for your site, you can always start a Live chat with our hosting support Superheroes or submit a support ticket using the Support tab of your WPMU DEV Dashboard.

WPMU DEV Support tab

WPMU DEV Max Upload File Size

The maximum file upload size for all WPMU DEV-hosted sites is 128Mb, regardless of hosting plan. Members can restrict the size of uploaded files, but the maximum size cannot be increased.

This cap should be more than enough for most sites, and is set on our managed WordPress hosting to limit the potential of attacks that can exploit large file size limits with huge post requests and overload your server.

Files larger than 128Mb should be uploaded by SFTP/SSH. See our SFTP & SSH documentation for information on how to upload large files.

To view the current maximum upload size for any site, navigate to the WordPress media uploader: Dashboard > WP Admin > Media > Add New. The upload size limit will be displayed at the bottom of the UI.

How to check max file upload limit

WordPress Default File Types

Members can add or remove file types from the allowed upload list as needed but should keep in mind that each added file type creates a potential security risk for your site or network. We recommend that you add only those file types you need.

WordPress allows uploading of these file types by default:

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

1.10.1 Multisite Upload Limits

Link to chapter 10

Multisite admins can adjust both the file size and file type limits in their Network Settings, located here: Dashboard > Network Admin > Settings > Network Settings.

Multisite file size and type limits

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

Upload Setting Multisite

Adding/Removing File Types in Multisite

In the Upload file types field, enter the file extensions of the file types you want to add, separating the extensions with a single space. Delete the extensions of file types you do not want to be uploaded.

Modifying file type and size limits

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 max size for files uploaded to this network.

Click Save Changes, and that’s all there is to it. The new file size limit will apply to every site within this network.

1.10.2 Standard Installation Upload Limits

Link to chapter 10

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

Failed file type security validation

Adding/Removing File Types in Standard Installations

We’re going to show you how the plugin WP Extra File Types can resolve either issue. The first thing to do is install and activate the plugin.

While we’re at it, we will show you how to use this plugin to identify why a file might trigger a security validation error, information that will be helpful if a particular file type or a particular user experiences ongoing upload issues.

Get WP Extra File Types

WP Extra File Types plugin

Once you’ve installed the plugin, you’ll find a new option, Extra File Types, in your site’s Settings tab, located here: Dashboard > Settings > Extra File Types.

Locating the WPEFT plugin menu

Click Extra File Types UI, and you will see a list of hundreds of file types from which to choose.

WPEFT plugin overview

You will also see two checkbox options, shown below. Do not select either of these boxes yet. Selective use of these options can help identify why a file triggered the upload error.

WPEFT optional features

Select the file type(s) you wish to add to the allowed list and then scroll to the bottom of the UI to click Save Changes.

WPEFT Save Changes button

Try to upload the problem file again, and if the upload succeeds, great! This means the file was simply not on the allowed list, and now it is. You and your users can now upload that file type as needed.

If the file triggers a validation error again, return to the WP Extra File Types UI, and select the Check only file extensions option shown below. Leave Skip WordPress checks unchecked, and click Save Changes. If the file is failing WordPress’s MIME type validation, this option will bypass that check without disabling other security measures.

WPEFT Check only file extensions button

Try to upload the problem file again, and if the upload succeeds, great! This means there was an issue with the file’s MIME type. Otherwise, the file was deemed safe to upload.

If the file triggers a validation error with Check only file extensions enabled, it’s time to consider whether you are certain the file is valid and not harmful. If you are uncertain, we recommend not uploading the file.

If you are certain the file is valid and not harmful, return to the WP Extra File Types UI. Uncheck the Check only file extensions option, and check the Skip WordPress checks option. Save your changes.

WARNING: Selecting this option will disable all WordPress upload security measures, and should only be used to upload files you are certain are not harmful. Leaving this option enabled allows users to upload any file type to your site, including potentially harmful files. You should disable this option when you are not actively troubleshooting an upload issue.

WPEFT Skip WordPress checks option

Try to upload the problem file again. If the upload fails with WordPress checks disabled, it is likely that the issue has nothing to do with the file type, and you should contact support for help troubleshooting the problem.

Adding Custom File Types in Standard Installations

You also can use WP Extra File Types to add file types not included with the plugin’s preset list. To do this, scroll to the bottom of the UI where you will find the Add your custom file types panel. Click the plus sign (+) to open the interface.

Adding custom file types to WPEFT

This will open up a table of fields where you must specify a file format by completing the Description, File Extension, and MIME Type fields. The Internet Assigned Numbers Authority (IANA) is responsible for all official MIME types, and you can find the information required for these fields on their Media Types page. Click Save Changes before returning to the media uploader.

1.10.3 Standard Installation Upload File Size

Link to chapter 10

Install the Increase Maximum Upload File Size plugin to make this task as easy as it can be.

Once the plugin is activated, Increase Maximum Upload File Size will appear as a new option near the bottom of your Admin Menu. Click the link to open the plugin.

WPIFS in the Admin menu

The plugin contains a single dropdown menu. When you open the UI for the first time, it will display your current max upload file size.

WPIFS UI

Click the dropdown menu to view the menu of various upload size limits. Setting a file size larger than 128MB will not override the 128MB max upload limit. Select the desired upload limit and click Save Changes.

Increase file size drop-down menu

Once a limit has been set, the plugin displays both the WPMU DEV Managed Hosting default limit of 128mb and the lower limit established by the plugin.

Choose file size limit WordPress

1.11 Getting .htaccess Support

Copy chapter anchor to clipboard

Our servers run NGINX, the fastest, most stable webserver type, and NGINX does not support .htaccess. Members accustomed to using .htaccess to enable or disable functionality needn’t worry. However, because all the functions typically associated with it are automatically handled by our servers.

Servers with the AllowOverride directive on, a prerequisite for .htaccess files, process requests at a much slower rate than NGINX servers. In fact, NGINX servers process many more requests per server than their Apache counterparts in large part because they don’t support .htaccess.

NOTE:

If your site has a .htaccess file in the root directory, WordPress or a plugin might attempt to write to that file when configurations change, but this is not a problem as our servers will simply ignore that file.

Some of the common uses for .htaccess that our servers automatically achieve are:

  • Permalinks – Our servers are configured to automatically handle permalinks for you.
  • Caching – Our servers handle caching for you, no need to install plugins or modify .htaccess files.
  • Redirects/rewrites – Redirects can be handled using a plugin or via custom server-side redirects that WPMU DEV support can install for you.
  • Security – Many WordPress security plugins have you modify the .htaccess file to install security rules. Fortunately, WPMU DEV hosting already has these security precautions in place at the server level.

Regardless of what you’re trying to achieve, if you’re doing it with .htaccess, then you’re probably doing it wrong. Instead, contact our support Superheroes, and they will help you figure out how to implement the same thing without creating or modifying a .htaccess file.

1.12 Getting nginx.conf Support

Copy chapter anchor to clipboard

As noted in the previous chapter, our server architecture is built on Nginx which does not support .htaccess. However, there may be times when you need some custom rules added to your server, to handle some plugin functionality for example.

As our system is managed WordPress, you do not have root access to the server, so cannot make those changes yourself.

In cases like this, simply contact our support superheroes via live chat or submit a support ticket using the Support tab of your WPMU Dev Dashboard, and we’ll be happy to make those changes for you.

create a new support ticket
Navigate to WPMU DEV DASHBOARD > SUPPORT > NEW TICKET to create a support ticket.

1.13 Restoring a Deleted Site

Copy chapter anchor to clipboard

A WPMU DEV hosted site can be deleted for any of the following reasons:

  • Automatically via CRON – If a site is unused, it gets automatically archived after 21 days as noted in the About Free Sites chapter above.
  • Deleted manually – You are free to delete any of your sites at any time.
  • WPMU DEV membership expired – If your membership at WPMU DEV expires, your hosted sites would also expire.

If you wish to restore a deleted site, the process is quite simple but it must be done within 30 days from the time it was deleted.

  1. Create a site while logged-in with the same WPMU DEV account, using the same temporary tempurl.host name & region as the original site.
  2. You’ll then see the backups of the original site available under the Hosting > Backups tab. Restore one of the available backups within 30 days, and your site will be live again.

1.14 WPMU DEV Server Error Pages

Copy chapter anchor to clipboard

Sites hosted by WPMU DEV display a clear white-labeled error page if there’s ever a server-side issue with your site. The available error pages are as follows.

Client error pages

401.html – Displays if the site has password protection enabled and the HTTP Auth form is dismissed by the user.

Default WPMU DEV error 401 page

402.html – Displays if the site is suspended due to required payment on your account.

Default WPMU DEV error 402 page

403.html – Displays if a connection is forbidden, possibly via a WAF rule.

Default WPMU DEV error 403 page

404.html – Displays when the URL or page requested by the user cannot be found.

Default WPMU DEV error 404 page

410.html – Displays if the requested page has been deleted permanently.

Default WPMU DEV error 410 page

429.html – Displays to a user/IP if they’re attacking /wp-login.php or /xmlrpc.php (see Bruteforce Attack Protection below).

Default WPMU DEV error 429 page

Server error pages

500.html – Displays if there is an internal server error.

Default WPMU DEV error 500 page

502.html – Displays if your server gets an invalid response from another web server.

Default WPMU DEV error 502 page

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

Default WPMU DEV error 503 page

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

Default WPMU DEV error 504 page

1.14.1 Customizing error pages

Link to chapter 14

You can take white labeling to another level by customizing the server error pages with your brand, or any custom information you may want.

So, for example, if you’re not too enthusiastic about our default error 500 page:

Default WPMU DEV error 500 page

You could create something much more suited to your brand:

Customized error 500 page example

How to customize

To create a custom page for any of the above errors, create a .html file with the error number as the filename, with any content you wish inside. Then upload it to the root of your WordPress install.

For example, to create a custom error page in the unlikely case something goes wrong on your server and you get the dreaded “500 internal server error”, you’d create a file called 500.html

Add any custom HTML content you like to your file, and upload. You can use the Manage Files utility from your Hub > Tools screen to create and add content to the file, or edit on your computer and upload via the File Manager or FTP.

Upload location for custom error page files

Here’s an example of the basic HTML you’d want to have in any custom error page:

Your custom pages can be as simple or as creative as you like, and branded however you need. If you need some inspiration, have a look at these pages for some great examples:
https://uicookies.com/500-error-page-templates/
https://freefrontend.com/html-css-404-page-templates/

1.14.2 More whitelabeling options

Link to chapter 14

Our White Label services allow you to remove all WPMU DEV branding so that you can use your own branding or even your client’s branding. This is largely offered as a tool through our WPMU DEV Dashboard Plugin. For a guide to rebranding with the WPMU DEV Dashboard Plugin, read our White Label Plugins document.

The process of white labeling your site is also closely linked to our Branda plugin. Branda simplifies white label branding, maintenance, and much more. Read our WPMU DEV documents on Branda to learn more about the plugin’s capabilities.

And if you’re using our Hub Client plugin to offer all the amazing site management tools of our Hub to your clients, you’ll want to review the Hub Client documentation as well.

1.15 Bruteforce Attack Protection

Copy chapter anchor to clipboard

All sites hosted by WPMU DEV have measures enabled at the server level to help prevent bruteforce attacks. This is to help ensure your site’s server never goes down due to a bot attack on the most commonly targeted WordPress URIs: /wp-login.php & /xmlrpc.php

Those URIs are continuously monitored on our hosting, and if either of them receives more than 1 request every 2 seconds (30 requests/min) from a single IP address, rate limiting will be applied automatically to block access to any user with that IP, and a 429 error page will be displayed to that user.

Default WPMU DEV error 429 page

This will throttle the connections a bit and help avoid having the server instantly go down due to an attack. If the connection is throttled 30 times within the last 30 minutes, then the attacking IP will be banned for 1 hour to help even more.

Any such 429 error will be logged by your server and can be viewed in the Access Logs in your Hub.

You can customize and brand the Error 429 page if you wish, just like any other default server error page, by following the directions in the Customizing Error Pages chapter above.

Note that only the URIs noted above are monitored, and rate-limited if attacked. For example, if you have modified your wp-login.php slug using the Mask Login feature in Defender, and that custom slug is discovered and attacked by a malicious bot, your custom login would not be protected by these measures. We, therefore, recommend that any such custom login not be too obvious; don’t make it easy for bad actors to guess.

Also note that, while these measures can help mitigate the effects of DoS/DDoS attacks, they should not be considered as full protection for such attacks. You may want to consider using the robust protection options offered by CloudFlare for that.