Managed WordPress – Frequently Asked Questions

We have collected some of the most common questions that customers ask about our Managed WordPress Hosting platform and housed them in one place.


1. How Can I Access the File Manager?

You can access the File manager by following this article. It will show you where to obtain your FTP and SSH credentials to log in to the server.

2. How Do I Make a Site Live?

Follow our helpful article on how to launch your site for the world to see!

If you are using Cloudflare for your DNS, please note that CloudFlare needs to be paused for the issuance of the SSL.

You can temporarily pause Cloudflare by:


1. Going to the Overview tab in the Cloudflare dashboard.
2. Expand the Advanced > section.
3. Click Pause.
4. Once the site is live you can Unpause Cloudflare.


Pausing Cloudflare will cause your origin IP address to be returned by Cloudflare’s nameservers, sending traffic directly to our servers rather than through Cloudflare’s reverse proxy.
Pausing Cloudflare will allow us to install the Let’s Encrypt SSL certificate on your Managed WordPress site. Once the site is live and has been renamed then you can resume Cloudflare.

3. How do I Make a Staging/Development Site?

Creating a staging/development site can help to create a site on a newer PHP technology or produce new content without making any changes to your production site. If you would like to create a staging/development site before you make any changes to your live site, you can follow the steps in this article:

4. How do I Take the Staging/Development Site Live?

To make your staging site the live site you will need to use our Migrate to Liquid Web Managed WordPress plugin. The plugin will take your staging site and replace your current live site with the staging site. This will take a few minutes to complete; while your files are transferring, your site will be temporarily inaccessible. To limit the downtime, you will want to do this outside of peak hours.

5. What is a Stencil and How Can I Use It?

A stencil will allow you to create a copy of any site you have and save it for another deployment without having to redo all the hard work you’ve put into customizing the site. Click on the following article to learn how to create a stencil site:

6. How Can I Increase My PHP Limits?

For an increase in PHP values, you will need to create a php.ini file. (Managed WordPress utilizes NGINX which does not read .htaccess files) To do so, you’ll first log in to your server with your SSH credentials. Once you are logged into the terminal you will type

cd /home/s#/html/

and replace s# with the user listed for the website.

In Managed WordPress you'll place the PHP values in the /html directory.


vim .user.ini

press i for insert and then paste these values into the file:

# Begin PHP Memory Limit
php_value memory_limit = 128M
php_value post_max_size 64M
php_value upload_max_filesize 64M
php_value max_file_uploads 64M
php_value max_execution_time= 300M
php_value max_input_vars = 259200M
php_value max_input_time = 259200M
php_value max_input_vars 9999M
# End PHP Memory Limit

Type Esc, and type

:wq to save your edits and exit.

These values are just an example of what you can put — you can increase or decrease the values for what you feel is appropriate for your website.

7. Why Didn’t My Plugins Update?

If your plugins didn’t update, you will want to login to the Managed WordPress dashboard and make sure that plugin updates are enabled. If the updates are enabled and your plugins are still not updated, please contact your Managed WordPress support team.In Managed WordPress you can toggle on and off automatic updates.

8. I Migrated My Site, But I Only See the Default Install. What’s Going On?

This usually happens when the PHP version is set too high for your site. You can adjust PHP versions by going into in the Managed WordPress Dashboard and under SITE DETAILS.In Managed WordPress you'll select the PHP version of your choice.

9. What Cache Plugin Should I Use To Speed Up My Site?

We include caching, so none are really needed, but these three plugins are the most frequently used by our customers and have seen the best results.

Free plugins:

Paid plugins:

The Best Ways to Secure WordPress

On our Managed WordPress hosting platform, we strive to ensure security with regularly scheduled patches and updates. By utilizing our intrusion prevention software, we mitigate malicious activity and block repeated failed logins for your WordPress admin portal. Furthermore, our web-application firewall, restricts unneeded ports along with custom rules to help protect you on the application level. We take care of the administration work so you can spend more time securing your site. Below our Managed WordPress admins share tested (and trusted) implementations to keep your site locked up tight.

WordPress Security Plugins

iThemes Security

The iThemes Security plugin is a fantastic addition to enhance your security, and it is easy to install.  By adding an extra layer of protection, below is a list of security features that iThemes Security Pro provides.

Click To See iThemes Security Features
    • Banned Users – Allows you to completely ban hosts and user agents from your site
    • Network Brute Force Protection – Banning users who have tried to break into other sites from breaking into yours. The network protection will automatically report the IP addresses of failed login attempts to iThemes
    • SSL – This feature redirects all http traffic to https
    • Strong Password Enforcement – Force users to use strong passwords as rated by the WordPress password meter
    • System Tweaks:
      • Disable Directory Browsing
      • Filter Suspicious Query Strings in the URL
      • Remove File Writing Permissions – Prevents scripts and users from being able to write to the wp-config.php file and .htaccess file
      • Disable PHP in Uploads – Disable PHP execution in the uploads directory. This blocks requests to maliciously uploaded PHP files in the uploads directory.
      • Disable PHP in Plugins – Disable PHP execution in the plugins directory. This blocks requests to PHP files inside plugin directories that can be exploited directly.
    • Change WordPress Salts – Use WordPress Salts to encrypt any passwords saved within WordPress, this adds an extra layer in password protection. Check this box and then save settings to change your WordPress Salts.

Salt Encryption Settings

  • WordPress Tweaks:
    • Comment Spam– Reduce Comment Spam
    • XML– RPC feature allows external services to access and modify content on the site. Common example of services that make use of XML-RPC are the Jetpack plugin, the WordPress mobile app, and pingbacks. If the site does not use a service that requires XML-RPC, select the “Disable XML-RPC” setting as “disabling XML-RPC” which prevents attackers from using the feature to attack the site. Disable Pingbacks – This feature only disables pingbacks. Other XML-RPC features will work as normal. Select this setting if you require features such as Jetpack or the WordPress Mobile app.
    • Block XML– RPC requests that contain multiple login attempts.
    • Restricted Access– Restrict access to most REST API data. This means that most requests will require a logged in user or a user with specific privileges, blocking public requests for potentially private data.
    • Force Unique Nickname– This forces users to choose a unique nickname when updating their profile or creating a new account which prevents bots and attackers from easily harvesting user’s login usernames from the code on author pages. Note this does not automatically update existing users; it will affect author feed urls if used.
    • Protect Against Tabnapping– Alter target=”_blank” links to protect against tabnapping. Enabling this feature helps protect visitors to this site (including logged in users) from phishing attacks launched by a linked site.
    • Login with Email Address or Username– By default, WordPress allows users to log in using either an email address or username. This setting allows you to restrict logins to only accept email addresses or usernames.

To install, login to your WordPress dashboard, click on “Plugins” on the left. Click on “Add New” and use the search box to find “iThemes Security (formerly Better WP Security)”. Click on “Install Now”, and then activate the plugin.  On the left bar, click on “Security” and iThemes will start a security check on your site.  Additionally, you can click on Security > Settings on the left to enable any security features that fit your website.


Wordfence Security – Firewall & Malware Scan plugin – Wordfence includes an endpoint firewall and malware scanner.  One of the key features is their threat defense feed arms that are supplied with the newest firewall rules, malware signatures and malicious IP addresses to keep your website safe.  Click on the Wordfence subtitle to jump to installation and setup instructions.


You can create an account with CloudFlare to help protect your websites from various attacks including DDoS mitigation, customer Cloudflare helps mitigate DDoS attacks, prevent customer data breaches, and block malicious bot abuse. Cloudflare DNS is DDoS protection for domain resolution. It sits behind the same 15 Tbps network that protects over 7 million Internet properties from denial-of-service attacks.  Cloudflare DNS also comes with built-in load-balancing, automatic failover, rate-limiting, and filtering. Cloudflare also offers DNSSEC to add a layer of trust on top of DNS by providing authentication.

Web Application Firewall (WAF)

Web application firewall (WAF) rulesets – Available on all of Cloudflare’s paid plans, the WAF has built-in rulesets, including rules that mitigate WordPress specific threats and vulnerabilities. Additional features: automatic cache purge, and header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled.  You can change Cloudflare’s settings from within the plugin itself without needing to navigate to the dashboard. The available settings to change are: cache purge, security level, Always Online, and image optimization.


As an auditing, malware scanner, and security hardening plugin, it’s a security suite that works well with your existing website’s  security. This plugin offers a great set of security features such as Security Activity Auditing, File Integrity Monitoring, Remote Malware Scanning, Blacklist Monitoring, Effective Security Hardening, Post-Hack Security Actions, Security Notifications, and Website Firewall (premium).

General Security Recommendations

We are living in an age where security needs to be updated at all times. Passwords is one of those crucial security mechanisms that needs to be updated at least every 30 to 60 days. The recommendation for each password complexity is to be at least 15 characters containing a combination of uppercase letters, lowercase letters, numbers, and symbols. The passwords should not contain dictionary words, usernames, personal information, or letter sequences. The passwords should not be reused in a given year.

Along with having secured passwords, your computer should also be protected.  Attackers can exploit computers that have outdated operating systems using worms, malware, Trojans, and viruses. You will need to make sure your computer has the latest security patches and fixes.  All browsers should be the latest versions. Do not install any software or browser plugins from any untrusted parties.  Install reputable anti-virus software and conduct regularly malware scans on your computer.

The most common source for malicious injections are vulnerabilities in CMS software, plugins, themes and other commonly used third party code. We recommend taking measures to update all CMS software, plugins and themes used to the latest versions available from their respective vendors. This would help limit the chance of future infections occurring.

Registering your website with Google Webmaster Tools will tell you the health of your website. Change the Default “admin” username.  Since usernames make up half of login credentials, having the username “admin” made it easier for hackers to do brute-force attacks.

Final Thoughts

Being at the top of your game on security is worthwhile to avoid paying expensive fees to clean up a hacked site, especially since there are many free security options at your disposal. Take a stroll through our Managed WordPress product page and discover how we can take the guesswork out of security. Along with a 24/7 support team at your fingertips, our Managed WordPress platform automatically updates plugins to reduce your site’s vulnerability to malware.

Exploring the CloudFlare Dashboard

Getting Started With CloudFlare™

Pre-Flight Check

Accessing the CloudFlare Dashboard

After logging into your Manage interface, click on Domains in the left menu and select the CloudFlare tab.

Each domain you’ve added to your CloudFlare account is listed here.

CloudFlare Dashboard Overview

Menu Bar

The menu bar at the top allows you to add new sites to CloudFlare by clicking on the blue Add Website button, or quickly narrow the number of domains displayed through the Search field. The Website column header also can be sorted alphabetically by clicking on its icon.

Domains List

  • The Status column shows at a glance whether CloudFlare is active on any listed domain, and can be clicked to quickly expand the domain’s dashboard.
  • A Quick Settings Menu, labeled , is located to the far right of the domain name. Clicking on it will allow you to pause CloudFlare, purge cached files, and perform other tasks without having to expand the domain’s dashboard.More button
  • To expand a domain’s full CloudFlare dashboard, you can either select “CloudFlare Dashboard” from the Quick Settings Menu () or click the [+] button to the left of the domain name.

CloudFlare Dashboard

Primary CloudFlare Dashboard

Once expanded, a domain’s CloudFlare Dashboard allows you to manage CloudFlare settings for the domain:

  • The Enable Development Mode link in the top-right corner will temporarily pause edge caching and minification so that changes made on your site can be seen more quickly.
  • The Pause CloudFlare link temporarily disables all CloudFlare services for the site.
  • Site Statistics are available in the top left corner, allowing you to see the number of cached and uncached requests processed through CloudFlare, and the amount of data included in those requests.
  • Clicking on the Caching Level setting allows you to choose between three levels:
    • No Query String, which only serves files from the cache when there is no query string (
    • Ignore Query String, which delivers the same resource to everyone, regardless of the query string (
    • Standard, which delivers a different resource each time the query string changes. This is the level recommended by CloudFlare.
  • The Purge Cached Files button clears any cached content from CloudFlare.
  • Clicking on the Auto Minify setting allows you to choose whether to removes unnecessary characters from your source code (like whitespace, comments, etc.) to reduce file sizes and lower the amount of data, which helps to reduce page load times. You can enable Auto Minify for CSS, javascript, and HTML files.
  • SSL Setup, available on paid plans, allows you to configure SSL settings on the domain.
  • The Security Level setting allows you to choose between four levels of protection:
    • Essentially Off: Provides a challenge to only the most grievous offenders.
    • Low: Challenges only the most threatening visitors.
    • Medium: Challenges both moderate threat visitors and the most threatening visitors.
    • High: Challenges all visitors that have exhibited threatening behavior within the last 14 days.
    • I’m Under Attack! Should only be used if your website is under a DDoS attack. Visitors will receive an interstitial page while CloudFlare analyzes the traffic and behavior to make sure they are a legitimate human visitor trying to access your website. This setting can be enabled quickly by clicking on the I’m Under Attack! button directly underneath the Security Level setting.
  • Clicking on your current Plan allows you to change the level of your CloudFlare service, from free to paid and basic to advanced. Premium features, including the CloudFlare firewall, are managed via the interface at CloudFlare’s website.
  • The DNS Settings link allows you to view and modify settings for the domain.

DNS Settings

Clicking on the DNS Settings link in a domain’s CloudFlare Dashboard brings up the current settings for the domain.

CNS settings in the CloudFlare dashboard

The Report DNS Changes button will allow you to add new subdomains to the domain, such as “” or “”. The DNS record values needed to configure your domain name for CloudFlare also are listed on this page for your reference.

How To Configure Your Server to Log Real Visitor IPs

Getting Started With CloudFlare™

Because CloudFlare acts as a proxy, all visits to your website and web applications will, by default, be logged as originating from a CloudFlare IP address — not the visitor’s actual IP address. However, the Apache module mod_cloudflare can be used to ensure that visitors’ actual IP addresses are logged and displayed.

We recommend that you activate mod_cloudflare as outlined in this article to accurately log website visitor IP addresses and prevent unwanted behavior. Without this step, your server’s firewall could block CloudFlare’s IP addresses, making your site inaccessible. If you need to check whether the module is already enabled or need assistance installing it, please open a ticket and Heroic Support® will be happy to help.

Pre-Flight Check

  • This article assumes that you have already set up CloudFlare and added your domain.
  • We’ll be installing the mod_cloudflare module for Apache, and you’ll need root-level SSH access to proceed.
  • If you’re using a web server other than Apache, you’ll need to enable the appropriate module for your web server. For Nginx, you can use the ng_http_realip_module, and an HTTP Module for IIS also is available.

Installing mod_cloudflare on CentOS 6 and CentOS 7 Servers with cPanel

To install mod_cloudflare on a cPanel server running CentOS 6 or CentOS 7, simply yum install our mod_cloudflare package:

yum install lw-mod_cloudflare-cpanel

We built the RPM in a way that does not require you to run EasyApache, because Heroic Support® is what we do 🙂

To confirm that the module has been added to Apache, run this command:

httpd -M | grep -i cloud

Installing mod_cloudflare on Core-Managed CentOS 6 and CentOS 7

To install mod_cloudflare on a core managed (non-cPanel) server running CentOS 6 or 7, simply yum install our mod_cloudflare package!

yum install lw-mod_cloudflare

To confirm that the module has been added to Apache, run this command:

httpd -M | grep -i cloud

Installing mod_cloudflare on Ubuntu/Debian Core-Managed Servers

To install mod_cloudflare on Ubuntu/Debian Core Managed, simply apt-get install our mod_cloudflare package:

apt-get install lw-mod_cloudflare

To confirm that the module has been added to Apache, run this command:

httpd -M | grep -i cloud

Next Step: Get to Know CloudFlare

Now that you’ve got everything configured, it’s time to Explore the CloudFlare dashboard.

How to Configure Your DNS for CloudFlare

Getting Started With CloudFlare™

Pre-Flight Check

  • This article assumes that you have already set up CloudFlare and added your domain.
  • We’ll be adding DNS records in Liquid Web’s Manage dashboard. If your site isn’t using Liquid Web’s nameservers, you’ll need to make changes at your registrar or DNS provider.
  • We’ll be using cPanel to set up an .htaccess redirect. If you don’t have access to cPanel, you will need to edit your .htaccess file directly; if you’re using a web server other than Apache (such as Nginx or IIS), you’ll need to set up the redirect manually. You can find tips for doing so in the bonus content section of this article.
Note: If your site’s DNS records are managed by CloudFlare or any other external source, our Heroic Support® team can provide the records you will need to add there to configure CloudFlare, but we will not be able to access your DNS records themselves.

Step #1: Get Your CloudFlare DNS Settings

  • Once your site has been added to CloudFlare via Manage, select Domains from the left menu, click on the CloudFlare tab and click the [+] button next to your domain name to expand the CloudFlare dashboard.
  • Now click on the DNS Settings link near the bottom-right corner to view your settings.View DNS Settings in the CloudFlare dashboard
  • The popup window will show you the specific changes you’ll need to make for your site:CloudFlare DNS settings popup

    Specifically, you’ll need to:

    • Add an .htaccess redirect to ensure all traffic to your site uses the “www” subdomain.
    • Add a CNAME record for the subdomain “”.
    • Change your CNAME record for the “www” subdomain to point to “”.

Step #2: Redirect Traffic to Your ‘www’ Subdomain

If you have access to cPanel, setting up the redirect is a simple process using the method detailed below. If you don’t have access to cPanel, though, you’ll need to set up the redirect manually. You can find tips for doing so in the bonus content section of this article.

  • Log into your site’s cPanel and click on the Redirects icon.cPanel redirect
  • You’ll set up the redirect on this page:
    • Set the Type of redirect to “Permanent (301)”.
    • Select your domain name from the http:// dropdown menu.
    • Leave the / field blank.
    • In the Redirects to field, enter the full URL to which you want to direct traffic. As shown below, it must include both the protocol and “www” subdomain. In this case, we want to redirect traffic for “” to “”, so we’ve put “” in the http:// field and “” in the Redirects to field.13cpanelredirect2
  • Once done, click the Add button at the bottom to put the redirect in place and move on to the next step.

Step #3: Add the CloudFlare Landing Page Record

  • In your Manage dashboard, select Domains from the left menu, then click on the DNS tab to see a list of your domains.
  • Now click the [+] to the left of your domain name to display all of its DNS records.Manage dashboard domain DNS
  • Click the Add New Record button in the bottom right to add the new record.Add DNS record in Manage
  • We want to add a CNAME record for the CloudFlare landing subdomain, so enter “cf-landing” into the NAME field, select “CNAME” for the TYPE field, and set the TTL field to a reasonable value. TTL, or Time To Live, tells DNS servers how frequently to look for changes to the record. The value is listed in seconds, 3600 (one hour) is typically sufficient. Once done, click the green checkmark button to add the record.Add a CNAME DNS record for CloudFlare
  • Review the record details in the popup window to make sure they match the values provided by CloudFlare, and click the Confirm button to add the record.Confirm the addition of a CloudFlare DNS record

Step #4: Change the Data Field Value for Your ‘www’ Subdomain

  • Locate the entry for your “www” subdomain and click the Edit button to change its value.Edit WWW record
  • In the DATA field, change the current value from your domain name to the value provided by CloudFlare. In this case, we’re replacing “” with “”. Because this is an existing record, DNS will abide by the record’s current TTL value; lowering it at this point likely will not speed up propagation, but you may want to check that it has a reasonable value.Change the value of your WWW record for CloudFlare

    Once you’ve entered the correct value, click the green checkmark button.

  • Finally, review the values presented on the popup window, and then click the Confirm button to add the record.Confirm www CNAME change
  • Once CloudFlare sees the DNS changes you’ve made, web traffic to your site will be routed through its servers. Note that it can take up to 24-48 hours for the DNS changes you made to fully propagate across the Internet, but in many cases you will see the changes take effect much more quickly.

Next Step: Configure Visitor Logging

Because CloudFlare acts as a proxy, sitting between your website and the rest of the Internet, your server will, by default, log all visits to your site as having originated from CloudFlare. Fortunately it is a simple matter to configure your web server so that site visitors’ actual IP addresses will be logged. Proceed to Part Three to get started.

Bonus: Domain Redirects for Sites Without cPanel

If you don’t have access to cPanel or are using a web server other than Apache, you’ll need to set up the “www” redirect manually. These instructions cover the general steps for popular web servers:


Apache redirects are accomplished via .htaccess files. The one you’ll need to edit will be located in your web site’s root directory, but you may need to check a box in your FTP client to show hidden files in order to see it. If you don’t already have a file named “.htaccess” in your site’s main directory, you’ll need to create one.

To redirect your non-www domain to www, simply add these lines at the beginning of your .htaccess file:

RewriteEngine on
RewriteCond %{HTTP_HOST} !^www.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301]


The non-www to www redirect can be made in IIS by adding the following redirect to the site’s web.config file:

<rule name="WWW Redirect" enabled="true" stopProcessing="true">
<match url="(.*)" ignoreCase="true" />
<add input="{HTTP_HOST}" negate="true" pattern="^www.(.+)$" />
<action type="Redirect" url="http://www.{HTTP_HOST}/{R:0}" appendQueryString="true" redirectType="Permanent" />


Nginx redirects may be configured in the site’s virtual host (.vhost) file or main configuration file, depending on the server version and operating system. Since Nginx is not supported by Liquid Web, we’re assuming that you already know how to edit the virtual host configuration.

To redirect your non-www domain to www, you’ll need to ensure that the primary server is configured to use only the “www” subdomain for its server name.

First, back up the configuration file and then locate the server block for your domain. If both the www and non-www versions of your domain name are listed in the same server block, remove the non-www reference to your site from that server name line. Then create a separate server block for the main, non-www, domain, similar to this one:

server {
listen 80;
return 301$request_uri;

This will direct all traffic directed at your site’s main domain to the www version of your domain name. Once you’ve finished, restart nginx for the change to take effect.

How To Add CloudFlare to Your Website

Getting Started With CloudFlare™

Pre-Flight Check

  • This article covers adding CloudFlare through your Liquid Web account and enabling it for a site you host here.
  • In this example, we’ll be setting up a new CloudFlare account for an existing domain that will continue to use its current nameservers.
  • Please note that to accurately log website visitor IP addresses and prevent unwanted behavior, we recommend that you activate the mod_cloudflare module on your server as detailed in Part III: How To Configure Your Server to Log Real Visitor IPs. Without this, your server’s firewall may block CloudFlare’s IP addresses, making your site inaccessible. If you need to check whether the module is already enabled or need assistance installing it, please open a ticket and Heroic Support® will be happy to help.

Step #1: Add CloudFlare to Your Account

  • In your Manage interface, click on Domains in the left menu and select the CloudFlare tab.CloudFlare panel in Manage->Domains
  • Enter the email address you want to associate with your account in the Email field and click the Let’s Get Started button to continue.
  • Within a few moments, you’ll receive an email from CloudFlare acknowledging that you’ve created the account.
    • The email will come from
    • Its subject will be “Welcome to CloudFlare, in partnership with Liquid Web”.
    • The email will include your CloudFlare username, a link to set your password, and a brief description of the service.
  • In the email, click the Claim your CloudFlare password at: link to set your password at CloudFlare’s website.Set password link in CloudFlare email
    Note: You’ll notice that the confirmation window at CloudFlare prompts you to “Reset Your Password”. Despite appearances, that does not indicate that you previously had set up a CloudFlare account using that email address; it simply uses the same language as the “forgot password” process on their site.
  • Enter your password twice to confirm it and then click the Reset Password button. Be sure to record your CloudFlare username and password in a safe location. It is separate from your Liquid Web account and not stored in our system. As such, we do not have the ability to provide it to you should it be lost. We can, however, assist with resetting it should that be necessary.CloudFlare password set
    Note: You’ll also receive an email confirmation from CloudFlare with the subject “Your CloudFlare password has been changed”. Once again, the word “changed” is due to the use of their password reset process to set your password, and — in this one specific instance — does not indicate that an existing password has been overwritten or that anyone besides you has made changes to your account.

Step #2: Add a Site to CloudFlare

  • Return to the CloudFlare tab in the Domains Dashboard of your Manage interface, and you will be able to add a new site to your CloudFlare account. To get started, click the green Add a Site button.Add a site to CloudFlare
    Note: You’ll only see the green Add a Site button when adding your first website to CloudFlare. Once a site has been added to your CloudFlare account, you’ll see a blue Add Website button which you’ll use to add additional sites.
  • Once you click the Add a Site (or Add Website) button, you’ll be presented with a popup window where you’ll enter the site’s details.Add CloudFlare site popup
    • Domain Name is the domain you’re adding. In this case, we’re using “”. Don’t enter the protocol (http://), and don’t include the “www”. Once you’ve entered the domain name, simply hit the tab key on your keyboard or click out of the field.
    • DNS Configuration lets you decide whether you will continue to use a site’s existing nameservers or CloudFlare’s. If you choose to use CloudFlare’s, you will need to manage your DNS records through your account there. As noted in the instructions for creating a CloudFlare account, we do not have access to your credentials there, and can not log in on your behalf to provide direct assistance setting up DNS records there if you need it. In this article, we will be using the site’s existing DNS provider (which is Liquid Web).
      • Subdomain lists the subdomain CloudFlare is protecting. In this case, because we’re setting up the main domain, it lists “www”.
      • Source Domain tells CloudFlare where to look for the source files for the domain name. This is the CloudFlare landing DNS record you’ll set up in Part 2.
      • Use the Add Another Subdomain button to add any other subdomains you’re currently using such as “” or “”. If you want to set up the main domain name now and return to this step, you can do so from the DNS Settings link in your CloudFlare dashboard by clicking the Report DNS Changes button.
    • CloudFlare Plan. This section lists the available service levels you can choose from, ranging from Free to Premium. All packages include CloudFlare’s global CDN, web optimization and security features, and unlimited bandwidth. The various paid packages include support for SSL certificates, Google’s SPDY protocol, mobile optimization, a web application firewall, and advanced DDoS mitigation.
    • Once you’ve chosen your desired level of service, click the Activate Service button under the name of the plan to add the site.Site is being added to CloudFlare
  • After a few moments you’ll see a “ready” message, indicating that the site has been added, and you’ll receive a welcome email confirming that the domain name has been added to your account. Click the “go to dashboard” link at the bottom and proceed to Part Two to configure the DNS settings for your domain and activate CloudFlare.Site successfully added to CloudFlare
    Note: At this point, you’ve added the site to CloudFlare, but you must complete the DNS setup to activate CloudFlare for the site.