The Tools usage guide is a detailed look at the features and configuration options located in the WPMU DEV Hosting Tools tab, which include:
- Password Protection
- Web Application Firewall (WAF)
- PHP Version
- Database Manager
- File Manager
- Object Cache
- Static Server cache
- Migrate Existing Site
Use the index on the left to locate usage guidance for a specific feature quickly.
If you have not set up a WPMU DEV hosting account, visit hosting to explore the features, pricing, and get a free trial.
Access your Hosting Tools from the Hosting tab by clicking the site you wish to manage.
Then, click the Tools tab.
5.1 Password ProtectionLink to chapter 1
You have the option of enabling ‘Password Protection’ on any site. Unlike your WordPress credentials, which control access to a site’s admin areas, Password Protection controls access to an entire site, meaning only those who know the password can work on or view a site. It even hides a site from search engines.
This is useful when developing a new site that you don’t want yet publicly available on the web. You can share the username and password with clients or colleagues, but unauthorized admin users and the general public will not have access.
Password Protection uses Basic HTTP Authentication and does not use any WordPress usernames or login details.
Users who attempt to access any part of your site will see a login modal similar to the one in the image below. Only by entering the correct credentials will the user be allowed to proceed.
Click the On/Off feature in the Password Protection row to enable/disable the feature. Use the toggle to turn site protection on or off.
Once active, create a username and password you wish to apply to this site. A strong password will be generated, or you can add a custom password into the field. When activating or deactivating your password, click Save to save your changes.
5.2 Web Application Firewall (WAF)Link to chapter 2
Our Web Application Firewall (WAF) monitors the IP addresses and user agents attempting to access your site and filters out traffic that is known to be unsafe or that you have identified as unwanted.
The key distinction between our WAF and typical site security protocols is that a security plugin protects a site at the point of attack, whereas a WAF prevents unwanted traffic from ever reaching its intended target in the first place (learn more about how WAFs work).
Our WAF protects sites from attacks such as cross-site request forgeries, cross-site-scripting (XSS), file inclusions, and SQL injections.
For additional steps in protecting your site, use Defender, and check out the Ultimate Guide to Security on the blog.
Configuring your WAF
A WAF requires all traffic to pass a set of rules that sits before traffic hits your WordPress site to help monitor and filter out attacks and malicious traffic. These policies aim to protect against vulnerabilities by filtering out malicious traffic. WPMU DEV has a custom set of WAF rules and allows you to add your own custom:
- IP Whitelist
- IP Blacklist
- User Agent Whitelist
- User Agent Blacklist
Click the On/Off feature in the Web Application Firewall row to enable/disable the feature, then click the toggle switch in the popup to access the configuration panel.
WPMU DEV maintains a set of rules that will identify and block known, unsafe traffic, but admins can whitelist (allow) or blacklist (block) IP addresses and user agents as they see fit using this configuration panel.
The IP or Internet Protocol address is a unique number that is linked to all online activity for a given user. You can block or grant access to specific machines, locations or users with the IP Whitelist/Blacklist fields.
You can Whitelist or Blacklist an IP address by entering it into the fields provided. Enter only one IP address per line, and click Change to save.
This makes it easy to block attacks quickly before they reach your server or whitelist your own IP or team member’s IP so they can bypass the WAF.
User Agent Whitelist/Blacklist
The user agent is the system information being used to access your site, including:
- The browser application name and version
- The host operating system and language
Often this information can be used to block a botnet that is originating from too many IPs to block but is using the same User Agent for its attack. You can view visitor User Agents in your access log.
Use the Whitelist field if you need to allow a good bot that doesn’t use specific IPs to bypass firewall rules. Remember, User Agents can easily be spoofed by bots, so whitelisting them should be done only when you can’t whitelist by IPs.
You can Whitelist or Blacklist user agent by entering it into the fields provided. Enter only one agent per line, and click Change to save.
Disabled Rule Ids
You can also disable specific firewall rule IDs that appear in the WAF log under the Logs tab (see below).
Remember, when activating, deactivating or editing rules in the WAF, click the Change button to save your changes.
WAF Logs for a specific site can be found in Hosting under the Logs tab.
Logs can be used to see where attacks are coming from, what requests were blocked, what rules those requests triggered, and changes that can be made to minimize false alarms. For example, if you are performing a valid action on your site and get blocked, you can find information on why in the WAF log and perhaps whitelist the IP or disable a specific firewall rule ID. More information about the WAF Logs can be found under the Logs document.
5.3 MultisiteLink to chapter 3
You can convert your site into a Multisite network by clicking the On/Off button in the Multisite row to open the configuration popup.
Once you’ve converted a site to a Multisite network, you cannot revert the site to a single site without migrating. So, before making the change, be sure converting to Multisite is the right move for your site.
If you are uncertain which Multisite installation– Subdirectory and Subdomain– is right for you, see our WordPress Multisite documentation for guidance.
Looking for help setting custom domain names for subsites on a Multisite network? Check out our domain mapping guide on the WPMU DEV blog.
When you’re ready, choose the Multisite installation you prefer and click Continue.
If you are absolutely certain you wish to continue, enter your WPMU DEV account password, check the Yes, convert my site to a Multisite box, and click Continue. The conversion begins immediately, and there is no way to stop it or easy way to revert the changes.
The time it takes to convert depends largely on the size of the site, but it could range from just a few seconds to several minutes. A success notification will appear in The Hub when the conversion is complete.
If you have chosen to go with a subdomain multisite, you will need to upload either a Wildcard SSL certificate or a certificate that covers all domains and subdomains that you plan to use. This will ensure that you can serve your domain over HTTPS, which we require. This is covered in detail in our Wildcard Certificates document.
It should be noted that wildcard certificates are not exclusively for subdomain multisites. You can also upload a wildcard SSL certificate for a subdirectory multisite, meaning that you can map subdomains to subsites in it, making your multisitse seem as if it is subdomain-based rather than subdirectory-based. In this case, you could even have both subdirectory-based and subdomain-based subsites in the same multisite. See our Wildcard Certificates document for more information on this.
5.4 PHP VersionsLink to chapter 4
It is our policy to only provide support for the latest supported PHP versions. This is both to make sure our sites are secure, and to provide you with the fastest most performant hosting service we can!
Currently we default all newly-created sites to the latest release of PHP 7.3. Occasionally, some third party plugins may be out of date and cause issues with the latest version of PHP. In that case you can look for updates, alternatives, or worst case, we do support downgrading your PHP version to older ones that still provide security patches (currently PHP 7.2).
If you want to test your site’s compatibility with the latest version of PHP before upgrading, we recommend changing the PHP version in your staging environment and testing the functionality there first.
You can upgrade or downgrade your PHP version in the Hosting Overview screen or in the Tools tab. In either case, click the edit icon next to the current PHP version number, and a list of available supported PHP versions will be displayed in the dropdown.
Choose the version you wish to install, and click Apply.
5.5 DatabaseLink to chapter 5
WPMU DEV gives you access to easily edit and manage your Database from the phpMyAdmin database manager.
Making changes to a site’s database can break the site. Take care when making changes. Contact support if you have questions. Detailed documentation for phpMyAdmin can be found on the phpMyAdmin site.
From the Tools tab, click the Manage Database link to open phpMyAdmin.
phpMyAdmin includes tools for managing and viewing databases:
- Status info
5.6 FilesLink to chapter 6
WPMU DEV also gives you access to easily edit and manage your website files using a file manager interface in case you don’t want to mess around with SFTP.
From the Tools tab, click the Manage Files link to open the File Manager in a new tab.
To help prevent inadvertent edits or deletions, core WordPress files are locked (read-only) and cannot be edited in the File Manager. If you absolutely do need to edit a core WP file, you will need to use an SFTP connection to do that.
The left panel allows you to navigate through files and logs from both the production server and the staging server.
The main toolbar at the top of the page offers features such as adding new folders and files, as well as uploading new documents.
If a tool is grayed out, it is unavailable for the selected location or document. To interact with folders and files without using the toolbar, right click on the location and a pop-up menu will appear. The pop-up menu includes features that are offered on the toolbar like open, download, and preview.
5.7 Object CacheLink to chapter 7
We leverage Object Cache at the database level, and this is enabled by default on all sites we host.
Object Cache improves performance by minimizing server load related to queries that are frequently called by WordPress, plugins, and themes. Because of this, you may need to clear Object Cache from your Hosting Hub after using a plugin that interacts directly with the database in ways outside of normal WordPress guidelines or if you make changes directly in your database using phpMyAdmin.
The object cache should only be flushed if absolutely necessary. It is usually not needed except after making direct database edits or during development. If you aren’t sure, contact support, and we’ll help you out.
To clear cache, click Flush in the Object Cache row.
A “Are you sure?” pop-up will verify you would like to clear your cache. Click Continue to flush object cache.
5.8 Static Server CacheLink to chapter 8
This is page caching at the server level using FastCGI. Much faster than any PHP plugin, Static Server Cache greatly speeds up your site and allows for an average of 10 times more concurrent visitors.
Static Server Cache is disabled by default on all hosted sites, but you can toggle it on by clicking the Off button to the right.
Then click the Continue button in the little modal that pops up to confirm the action.
Once enabled, simply click the Clear button if you need to clear the Static Server Cache, then click the Continue button in the modal to confirm.
Our Static Server Cache is fully integrated with our Hummingbird performance plugin, meaning that any action or process in Hummingbird that triggers the clearing of page cache will also clear the Static Server Cache.
So if you have Page Caching enabled in Hummingbird, and click a Clear Cache button in the plugin, Static Server Cache will clear as well. Or if you have options like “Clear cache on interval” or “Clear full cache when post/page is updated” enabled in Hummingbird, Static Server Cache will respect those settings too.
WooCommerce is supported by default, meaning that any dynamic process in Woo is not cached. So if a user adds items to their cart, etc, that would not be cached by the Static Server Cache, so no worries there.
What does it cache exactly?
The following should give you a good idea about what does and does not get cached when Static Server Cache is enabled.
- GET/HEAD requests are cached (that’s your content; meaning all your posts, pages, etc.).
- POST requests are skipped (for example, forms or any other frontend submission).
- Query strings are skipped.
- wp-admin, xmlrpc, wp-*.php, feed, index.php, sitemap URIs are skipped.
- Cache is skipped if these cookies are found: comment_author, wordpress_, wp-postpass, wordpress_no_cache, wordpress_logged_in, woocommerce_items_in_cart.
- Cache is skipped if these WooCommerce URIs are found: /store, /cart, /my-account, /checkout, /addons.
Static Server Cache clears automatically every hour, and the max size of any item is 1Gb.
How to see if it’s working
To check any page to see if it’s being cached by our Static Server Cache, pop open your browser’s developer tools, and click on the Network tab. Then reload your page.
Have a look at the Response Headers for the main document type of your page, and look for x-cache where you’ll see the following possible values.
- x-cache: BYPASS – Cache is bypassed for any reason (URL parameter, cookie, WooCommerce, logged in etc.).
- x-cache: MISS – It will be cached on next page load.
- x-cache: HIT – Cache is served.
5.9 Reset wp-configLink to chapter 9
This file is located in the root of your WordPress file directory and contains your website’s base configuration details, such as database-connection information. If you migrated a site from another host, this information might need to be reset.
Clicking reset will open the “Reset wp-config.php” confirmation pop-up. This will reset your wp-config.php back to the default state, and anything you have added or changed in it will be lost.
Click the Confirm Reset button to reset the wp-config.php file or the X or Cancel to close without saving your changes.
5.10 Migrate Existing SiteLink to chapter 10
- During migration, the source site overwrites everything on the destination site, including all content, plugins, themes and settings. Be sure this is what you want before proceeding.
- If you don’t have (S)FTP access to the site you want to migrate here, you should be able to create (S)FTP credentials in your current host’s control panel. Or you can try automated site migration with our Shipper plugin, instead.
To Migrate to a new Hub-connected site, click the Begin Migration link in the Migrate Existing Site row. From the dropdown, choose a location from the dropdown to migrate to.
If you don’t see the site you wish to migrate to, Add it to your Hub first and refresh the list.
Click Next to continue.
On the next screen, enter the (S)FTP credentials for your site. You should be able to view or create (S)FTP credentials in your current host’s control panel, or you can try migrating with the Shipper plugin instead.
Once you’ve entered the information, click Start Migration to continue.
If you encounter any issues with migrating your site or using or configuring the Tools, Members have 24/7 support and site migration assistance.