How to Add or Modify DNS Records in Manage

Pre-Flight Check

To manage a domain’s DNS records in your account management interface, it must use one of our nameservers, which are:

  • ns.liquidweb.com and ns1.liquidweb.com
  • ns.sourcedns.com and ns1.sourcedns.com

If you already know that your site is using Liquid Web’s nameservers, skip ahead to Step #2: Adding or Editing a DNS Entry.

Step #1: Where is DNS hosted?

There are several methods to determine which nameservers are considered authoritative for your domain. You can either:

  • Use a web-based WHOIS lookup tool such as ICANN WHOIS and noting the listings under Name Servers
  • Query WHOIS from a terminal by running the command “whois yourdomainname.com” and noting the listings under Name Servers
  • Log into your Manage interface, select Domains from the left menu and click on the DNS tab. Scroll down to the CURRENT DNS ZONES section and look at the Delegation column. If you see a green button labeled “Delegated”, your domain is using our nameservers and you can click the [+] the the left of the domain name to expand its record and start managing entries immediately.

    CurrentDNSZones

If your domain is not using our nameservers but you do want to be able manage DNS records through your Liquid Web account interface, you will need to log into your account at the registrar and update the nameservers to one of the pairs noted at the top of this article.

Note: It is not necessary to transfer a domain name simply to specify different nameservers or move its authoritative DNS record. You can continue to use your preferred registrar for domain name renewal and management even if you update the domain to use our nameservers.

 

Step #2: Adding or Editing a DNS Entry

  1. From your Manage interface, click on Domains in the left menu and then select the DNS tab in the Domains Dashboard and click the [+] to the left of the domain name to expand its DNS record.

    Add a DNS record in Manage

  2. To add a new record, click the blue Add New Record button at the bottom. To edit an existing record, click the Edit button to the right of the entry you wish to change. Each entry has four fields:

    Add new DNS record

    • Name: This field allows you to append a prefix (or more accurately, a suffix, since domain names are resolved from right to left) to the main domain name. If you’re adding a record for a subdomain, such as shop.example.com, you would enter “shop” in this field. Note: The Name field is also called “Host” or “@” at some registrars and hosting companies.
    • TTL: This specifies, in seconds, how long the DNS entry should be cached by a resolver before it’s considered outdated and checked again. A higher setting will reduce load on the DNS server, but will extend the time it takes for the new entry or value to propagate. Generally, you will want to set a lower value prior to changing a record (300 or 3600 for 5 minutes or one hour, respectively), and then raise the TTL back after 24 to 48 hours once your change has had a chance to fully propagate.
    • Type, and Data: Manage allows you to enter and edit multiple record types. Remember that only A, AAAA, and NS records take an IP address in the Data field.
      • A and AAAA records resolve a domain to an IP address (IPv4 for A, IPv6 for AAAA). Without these records, a site will not resolve. In addition to the main domain name, you likely will want to add an A record for your hostname, as well as any subdomains which resolve to a different server.
      • CNAMEs are aliases pointing an entry back to the main domain. Once a browser requests a page from that subdomain from your web server, the server will route the request to the proper directory. If you find yourself frequently creating records for subdomains, you may wish to add a wildcard CNAME to cover any requests for subdomains without their own records. You can do so by entering an asterisk in the Name field.
      • MX records determine how mail is handled for the domain. When selecting an MX record type, Data will contain two fields: Priority and Exchange.
        • Priority always will be a number. Mail will be routed to the lowest numbered (highest priority) MX entry. Use the settings recommended by your control panel or email provider.
        • Exchange is the server to which mail will be directed.
      • NS Nameserver records specify the nameservers for the domain. Remember that the authoritative nameservers are specified at the registrar — if a WHOIS search returns different nameservers than what you’ve entered here, your entries in Manage will have no effect.
        Note: When using your own private or custom nameservers, their nameserver entries must be added at the domain’s registrar. When using custom nameservers, you will not be able to use Manage to add or edit DNS entries; that will be done via your server’s control panel.
      • SRV, or Service, records are used to configure services for your domain. When configuring an SRV record in Manage, the Name field should begin with an underscore, then the name of the service, a period, an underscore, and finally the protocol. For instance, a SRV record for Office 365’s Session Initiation Protocol over TLS would contain “_sip._tls” in the Name field. An SRV record contains four Data fields, each of which should be filled out according to the service’s instructions:
        • Priority: As with MX records, the lower the number the higher the priority.
        • Weight: Is used to distribute requests based on capacity.
        • Port: Directs requests to a specific port.
        • Target: Specifies the destination. For the example Office 365 SRV record above, the target would be “sipdir.online.lync.com”.
      • TXT records contain, as the name suggests, text. They can be used for SPF and rDNS entries, as well as domain verification information.
  3. Once you click the green checkmark button, the record will be added and DNS will begin to propagate. Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally.

 

How To Enable Server Backups in WHM/cPanel

The most important thing you can do to protect your server against data loss is to take regular backups. Properly configured backups are a critical aspect to the maintenance of any website, and can mean the difference between a quick recovery and rebuilding a site from scratch.

If a key file were to accidentally be deleted, a site database were to become irreparably corrupted, or your site were to become infected with malware, would you be able to restore your data and get your site back up within a few minutes? If you can’t answer “yes”, then it’s time to review your backup strategy.

Liquid Web customers have access to a variety of backup methods including Guardian and Storm® backups, but this article focuses exclusively on cPanel backups. Because cPanel backups are not managed by Liquid Web, you will want to ensure that you have both enabled backups as described in this article and formulated an appropriate backup retention policy. It’s critical that you not attempt to store so many backups that your server runs out of disk space. In fact, you ideally want to reserve at least 10 percent to 20 percent of your total disk space: cPanel needs to (temporarily) use disk space to create backups and update itself and other software packages, and your operating system and database both rely on having disk space available to perform core functions.

Pre-Flight Check

  • This article covers backup configuration in WebHost Manager using cPanel’s “new” backup system. Legacy backups still are supported in cPanel for backward compatibility, but the current system is preferred as it is designed to be more efficient and reliable.
  • While these instructions specifically apply to WHM version 54.20; the same steps should apply to any recent cPanel version.

Step #1: Configure Global Settings

Log in to WHM using your server’s root credentials, and select Backup Configuration under the Backup section in WHM’s main menu. You can begin typing “backup” into the search menu to narrow the list of menu options.

WHM backup

In the Global Settings section. select the radio button next to Enable to turn on the backup system.

Note: The Enable button only turns on the backup system; you still need to instruct cPanel to back up accounts, and which accounts to back up, which we cover later in this article.

Now choose the type of backups you want cPanel to create:

  • Compressed backups use the least amount of disk space, potentially giving you more restore points than could get with the other methods. Compressed backups take longer to complete and the process of restoring an individual file requires the extra step of first extracting the file, but in many cases it represents an ideal option. Note that the size of a compressed cPanel backup will range from about 25% to 75% of the actual account size, depending on a number of factors, such as the types of files owned by the account. Until backups have run and you can see the actual size of each archive, it’s generally safe to estimate that a compressed backup will take up about half the space of the account itself. Once backups have run, you can use the actual figures to determine how many compressed backups to retain.
  • Uncompressed backups can be completed faster, and the process of restoring individual files is quicker because they don’t first need to be extracted from the archive. However, they take up the same amount of space as the account itself and, as such, allow for fewer restore points. If you choose to use uncompressed backups, you must ensure that your retention policy does not allow you to run out of disk space.
  • Incremental backups allow you to retain only one daily, weekly, and monthly backup, giving you fewer restore points than either of the other options. The backups are uncompressed, so each will take up the same amount of disk space as the account itself. Individual files can be quickly restored, but changes to your files are synced each time backups run. That means that a corrupted, compromised, or changed file you wish to restore could already have been synced to your backup if the change isn’t immediately noticed.

Step #2: Choose Scheduling and Retention Options

The Scheduling and Retention section allows you to enable or disable daily, weekly, and monthly backups, and specify the number of each type of backup you wish to store. For daily and weekly backups, you can select the days of the week on which backups will be taken and, for monthly backups, you can select whether you want them to be taken at the beginning of the month, in the middle of the month, or both.

Scheduling and retention

Note: If you select both the first of the month and the 15th of the month for monthly backups to run, each will count as one monthly backup. When choosing both backup date options, you will need to retain two monthly backups for each month you wish to retain.

Step #3: Select Account Backup Options

The Files section allows you to select which accounts to back up and choose more detailed options for each:

FilesBackupAccounts

  • We enabled the backup system itself in Global Settings above, and now we’ll instruct cPanel to back up user accounts by checking the box next to Backup Accounts.
  • Click the Select Users to open a new browser window (or tab, depending on your browser settings) where you can select the specific cPanel accounts to back up. Simply click the ON button in the Backups column for each domain you want to back up, and ensure that the buttons in the Legacy are turned off if you’re not using the legacy backup system. Note that you can access this page directly at any time by clicking Backup User Selection in WHM’s main menu.

    BackupUserSelection

    Choose whether you want to back up accounts that are suspended, as well as access logs and bandwidth data for the accounts, and whether you wish to back up system files as well as individual accounts (which is necessary only for server restoration; individual account can be restored regardless of your choice here).

Step #4: Select Database Backup Options

In the Databases section, select whether you want to back up databases per account, the entire MySQL directory, or both. In most cases, you’ll want to choose Per Account and Entire MySQL Directory.

BackupDatabases

Step #5: Select Backup Location

The Configure Backup Directory section allows you to choose whether you want to back up locally or externally.

BackupDirectory

  • The Default Backup Directory is pre-configured, and in most cases should not be changed.
  • If you elect to Retain backups in the default backup directory, local backups will be retained even if you configure the server to automatically transfer them to an external destination.
  • The Mount Backup Drive as Needed option should, in most cases, remain disabled, as an external drive set up by Liquid Web will be configured to mount at boot.

Step #5: Select Remote Transport Options

The Additional Destinations section allows you to set up a method for transferring your backups off-server via SFTP or another method. To do so, select a Destination Type, click the Create new destination button and provide the requested credentials on the form.

AdditionalDest

Step #6: Review and Save Backup Settings

Once you’re satisfied with your backup configuration, click the Save Configuration button to apply your settings.
 

How To Add a DNS Record For Your Hostname in Manage

Pre-Flight Check

  • These instructions are intended for domain names using Liquid Web’s nameservers.
  • If the main domain uses other nameservers, such as at a registrar, you will need to log in there and add an “A” record for the hostname in the main domain’s DNS zone file. The record should point to the server’s primary IP address.

Whenever you create a new server (or change the name of an existing one) you will need to add (or update) the DNS record for its parent domain.

If the hostname does not resolve, you will not be able to:

  • access WHM, cPanel, or Webmail via the hostname
  • send or receive email over a secure (SSL) connection using a mail client
  • verify the authenticity of email sent by the server (which could result in mail being rejected or flagged as junk by the recipient’s server)

Fortunately, adding the record is a simple process, and you can add the record in your Manage dashboard.

  1. Once logged into your Manage interface at https://manage.liquidweb.com/manage, click on Domains in the left menu and then select the DNS tab in the Domains Dashboard.

    DNS zones

  2. Now, click the [+] next to the main domain name to expand the domain’s DNS record and click the Add New Record button at the bottom. For the host.examplesite.com server, we’ll be editing the DNS record for the main domain, examplesite.com.

    Add a DNS record in Manage

  3. Your hostname will need an “A” record pointing to the IP address of the server itself. In this case, because the server has only one IP address, it is the same as the IP address of the site.

    Add new DNS record

  4. Once you click the green checkmark button, the record will be added and DNS will begin to propagate. Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally.

 

How To Restore Managed WordPress Backups

Pre-Flight Check

  • This article applies specifically to Liquid Web’s Managed WordPress servers.
  • Restoring a site from backup will completely overwrite all of its existing content (both the files and the database). If you are not completely certain that the existing files will no longer be needed, you may wish to back up the database and download the database backup and site files locally using SFTP with a client such as FileZilla.

Managed WordPress sites installed via the Sites tab in Manage automatically are backed up each day, with the server retaining the 10 most recent backups. You can easily restore any site from an available backup in the Sites dashboard in Manage.

Step #1: Open the site in the Sites dashboard

Click on the [+] next to the domain name to expand the window, then select the desired restore point from the Automatic Backups section.

Select A Restore Point

Step #2: Restore the Site

  1. After clicking on the radio button next to the desired restore point, click the Restore button to restore the site. A confirmation window will pop up to remind you that you will be overwriting the existing site with the contents of the backup. Any changes made to the site since the chosen backup was made (comments, posts, etc.) will be completely overwritten and can not be recovered. If you wish to proceed with restoring the site, click the Restore WordPress Domain button.
    If you are not completely certain that the existing files will no longer be needed, you may wish to back up the database and download the database backup and site files locally using SFTP with a client such as FileZilla.

    Confirm the Restore

  2. The restoration process will begin, and you will see a banner at the top of the page alerting you that the process is under way. The time it will take to complete depends entirely on the size of the site directory and database.

    Restore Complete

 

Using WP-CLI With Your Managed WordPress Site

Using the Command Line Tools

Liquid Web’s Managed WordPress servers come with a pre-installed set of command-line tools designed to simplify common site maintenance tasks. WP-CLI (WordPress Command Line Interface) can be accessed via SSH, and allows you to do nearly anything that can be done from within the WordPress admin interface.

Among many other things, WP-CLI can be used to:

  • create and modify users and their roles
  • install and activate or deactivate plugins
  • perform basic database maintenance tasks
  • manage cron jobs
  • manage rewrite rules

For the full list of commands, visit the official documentation.

WP-CLI always should be run as the site owner, and always should be run from within the site’s installation directory. For the following examples, I have connected to the server via SSH using the WordPress admin credentials for examplewordpresssite.com, verified my current working directory with the command “pwd”, and then changed directory into the site’s document root with the command “cd”, running “pwd” once again to confirm that I am in the document root.

[examplesiteuser@wphost]# pwd
/home/examplesiteuser/
[examplesiteuser@wphost]# cd public_html
[examplesiteuser@wphost ~/public_html]# pwd
/home/examplesiteuser/public_html

Create a New User and Assign a Role

In this example, we’re going to create a new user named “sample”, assign them the role of Editor on the site, and email them their credentials (a randomly-generated password will be assigned automatically, and the email is sent to their specified address with a link to reset it.):

wp user create sample sample@examplewordpresssite.com --role=editor --send-email

Breaking down this command:

  • wp invokes WP-CLI
  • user create creates the new user
  • sample is the name we chose for the new user
  • sample@examplewordpresssite.com is the new user’s email address
  • –role=editor assigns the role of Editor to the new user
  • –send-email instructs WordPress to email the user’s credentials, and a link to change their password, to the new user’s email address

Install and Activate a Plugin

Here we’re going to download, install, and activate the Meta Slider plugin from wordpress.org.

While we know the name of the plugin, the plugin’s actual file name may be different, so we first will run a search to find out, using the command:

[examplesiteuser@wphost ~/public_html]# wp plugin search metaslider

Running that command tells us that the plugin’s name is “ml-slider”:

[examplesiteuser@wphost ~/public_html]# wp plugin search metaslider
Success: Showing 4 of 4 plugins.
+----------------------------+----------------------------+--------+
| name | slug | rating |
+----------------------------+----------------------------+--------+
| Meta Slider | ml-slider | 96 |
| ThreeWP Broadcast | threewp-broadcast | 94 |
| EWWW Image Optimizer | ewww-image-optimizer | 90 |
| EWWW Image Optimizer Cloud | ewww-image-optimizer-cloud | 90 |
+----------------------------+----------------------------+--------+
[examplesiteuser@wphost ~/public_html]#

Now that we know the file name of the Meta Slider plugin, we can download, install and activate ml-slider with the following command:

wp plugin install ml-slider --activate

Running that code generates the following output:

[examplesiteuser@wphost ~/public_html]# wp plugin install ml-slider --activate
Installing Meta Slider (3.3.6)
Downloading install package from https://downloads.wordpress.org/plugin/ml-slider.3.3.6.zip...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Success: Translations updates are not needed for the 'English (US)' locale.
Activating 'ml-slider'...
Success: Plugin 'ml-slider' activated.
[examplesiteuser@wphost ~/public_html]#

The “Success” messages tell us that ml-slider was installed and activated.

Database Operations

WP-CLI has a number of basic database management features built right in.

Back Up A Database

One particularly useful WP-CLI command allows you to easily back up the WordPress database:

wp db export

Running that command will export the site’s database to an sql file in the current working directory. If you do not specify a name for the file, the exported database file will be the database name with a “.sql” extension, and any existing file with that name will be overwritten. Because we are backing up the database and don’t want this file to overwrite any previous versions, we will be specifying a file name (which must end in .sql).

[examplesiteuser@wphost ~/public_html]# wp db export mydatabase_01042016.sql
Success: Exported to mydatabase_01042016.sql

You always should back up the WordPress database prior to making any significant changes. It takes only a moment and ensures that you will have a restore point in case your changes don’t quite go as planned.

Restore A Database

You can quickly restore a database from an sql file with:

wp db import

Simply supply the file name of the database to restore, and the specified sql file will overwrite the existing database:

[examplesiteuser@wphost ~/public_html]# wp db import mydatabase_01042016.sql
Success: Imported from mydatabase_01042016.sql

Note that importing a database will completely overwrite the existing database. Do not import a database unless you are certain that you have no further use for the existing database or its contents. If in doubt, back up the current version with a unique file name before restoring.

Search and Replace in the Database

WP-CLI includes an advanced search and replace that can be used for delicate operations on database tables. This feature commonly is used to update references to the site name when taking a development site into production.

In this example, we’re going to change the name of the user we created earlier, “sample”, to “example” using the command “wp search-replace”. Note that we’ve already backed up the database above using “wp db export”.

And because we’re changing a username, we’ll also specify that we want only to include the wp_users and wp_usermeta tables in the search and replace, so that the word “sample” doesn’t get replaced with “example” in posts or anywhere else it may crop up:

wp search-replace 'sample' 'example' wp_users wp_usermeta

Breaking down that command:

  • wp invokes WP-CLI
  • search-replace searches for the specified string and replaces it in the specified tables
  • ’sample’ is the string we’re searching for (the old text). The search string needs to be enclosed in quotes.
  • ’example’ is the string we’re replacing the old text with. The string needs to be enclosed in quotes.
  • wp_users wp_usermeta are the specific tables to which we are restricting the search and replace. You can list as many table names as necessary, separating them with a space. If no table name is specified, the search and replace will be performed on the entire database. Performing a search and replace on the entire database is a potentially dangerous operation and should be done only if you are absolutely certain of the results and even then, only after backing up the existing database with a unique name.

 

Note: Do not attempt to run a search and replace (or any other database-altering procedure) without first backing up the database with a unique file name. Even the simplest search and replace has the potential to cause a great deal of damage, or even take the site down (consider the result if we had replaced the word “sample” with “example” in every table in the database for a product sample giveaway site). Always manually take a database backup with a unique file name before running search-replace.

Manage Cron Jobs

WP-CLI can be used to display scheduled cron jobs, run them manually, or even add new ones.

For instance:

wp cron event list

returns a list of all scheduled WordPress crons.

You also may choose to run a listed WordPress cron immediately:

wp cron event run wp_scheduled_delete

executes the wp_scheduled_delete cron event right away, instead of at its normally scheduled time.

Manage Rewrite Rules

WP-CLI gives you the ability to see current rewrite rules as well as change the rewrite structure:

wp rewrite list

displays all current rules.

You also can change the rewrite structure using default WordPress variables. To make your rewrites display the month number first, followed by the year and the name of the post, you would use:

wp rewrite structure '/%monthnum%/%year%/%postname%'

Multisite WordPress Installations

Nearly all the WP-CLI commands can be used the same way on multisite installs as well, so long as you specify the site in the command. This is done by specifying the URL (in the format: –url=domainname.com) in the command.

For example, the command to list scheduled crons for examplewordpresssite.com on multisite would become:

wp cron event list --url=examplewordpresssite.com

Get Involved!

There is a great deal more that can be accomplished with WP-CLI, including the ability to write your own commands and share them with the WP-CLI community.

To get started, check out the Github page and the list of current community commands.
 
 

How To Connect To Your Managed WordPress Site Using SFTP

Pre-Flight Check

  • SSH File Transfer Protocol (SFTP) is the most secure way to upload files to your Managed WordPress site.
  • This article is intended specifically for connecting to a Managed WordPress site using the free, cross-platform FTP client FileZilla, but the connection details should apply to any FTP client.

Step #1: Enter the Connection Details

  1. FTP/SFTP connection details are included in the “Welcome to your new WordPress site” email that was automatically sent to you upon adding the site in the Sites section of your Manage dashboard. In case you don’t have that handy, you will use:
    • Host: The domain name or IP address of the site
    • Username: The WordPress admin username created when adding the site
    • Password: The password you assigned to the WordPress admin user when adding the site
    • Port: 22 (Port 21 can be used for a standard FTP connection, but it is not recommended. SFTP should be used for maximum security. All connection details other than the port number are the same either way.)
  2. In FileZilla, enter the host, username, password, and port into the Quick Connect toolbar and press the Quickconnect button.

    FileZilla QuickConnect

Step #2: Security Settings

If your site does not yet have its free standard SSL certificate installed, you will need to click OK to accept the “Unknown host key” message and proceed with the connection. The connection still will be secure, but will be encrypted using the server’s self-signed certificate. When you’re ready to get your site’s free standard SSL certificate ordered and installed, please contact Heroic Support®.

Unknown Host Key

Step #3: Upload Files

Once connected via SFTP, you will be able to securely transfer files to and from the server. You initially will connect to your account’s home directory (/home/username/), and will need to navigate to the appropriate directory for the content you are uploading. In FileZilla, you can paste the desired path directly into the Remote site field. For reference:

  • Document root: /home/username/public_html
  • Plugins: /home/username/public_html/wp-content/plugins
  • Themes: /home/username/public_html/wp-content/themes
  • Uploads: /home/username/public_html/wp-content/uploads

File locations
 
 

Adding Sites To Your Managed WordPress Server

Pre-Flight Check

  • This article applies specifically to Liquid Web’s Managed WordPress servers.
    We will be adding a WordPress site directly through the Manage interface, the preferred method for Managed WordPress servers.

Step #1: Open the Server Dashboard

  1. Log into your Manage dashboard and click the [+] button to the left of your Managed WordPress server’s name to expand the dashboard.

    Open the Dashboard

  2. Click on the Sites button in your dashboard to launch the WordPress Sites view.

    Click on Sites

Step #2: Add A Site

  1. To add a site, click the Install a WordPress Site button, fill out the requested information, and then click Add Site to add the new site.

    Add a Site

    • Domain Name is the domain name you want to add to the server. If the domain name is using Liquid Web nameservers, a free SSL certificate will be ordered and installed on the domain, and WordPress will be configured to use the https protocol on the site. If the domain name is pointed elsewhere, an SSL can be added later.
    • Username is the WordPress admin user. The username specified here will be used to log into both WordPress and the site’s cPanel account. It must be 16 characters or fewer.
    • Email is the contact information for the site.
    • Password is the credential which will be used to log into both WordPress and cPanel. It should be a strong password, and can contain upper- and lower-case letters, numbers, and basic special characters such as underscores.
    • Verify Password requires you to enter the password again, and will alert you if it does not match what was entered on the Password field.
    • Automatic Updates allows you to choose between automatically updating WordPress itself (Core), WordPress and its plugins (Core and Plugins), or disabling automatic updates altogether (None). It is recommended to at least enable automatic updates for WordPress itself.
  2. The site now will be listed in your Sites dashboard, where you can change update preferences or install a free standard SSL on the domain.

Step #3: Review Settings

Once you return to the Sites dashboard in Manage, you’ll now see your new WordPress site listed in the WordPress Sites section. Click on the [+] next to the domain name to expand the view and configure options for the site.

Review Settings

  • Automatic Updates: You can choose to have the WordPress core or the WordPress core and all plugins updated automatically, or you can disable update Automatic Updates altogether. Simply click the Update button after making any changes to the selected option.
  • Automatic Backups: The WordPress installation automatically will be backed up on a daily basis, and 10 of the daily backups will be retained. Beginning on the 11th day, the oldest backup automatically will be deleted when a new one is created. You will see a list of each backup listed under Automatic Backups once the first backup has been taken.
  • Install Free Signed SSL: Automatic SSL installation is possible only when the site’s domain name is registered and pointed to Liquid Web’s nameservers. If the domain is new or using other nameservers, you can click Install Free Signed SSL to get an SSL certificate for the domain ordered and installed at no charge.
  • Note that Managed WordPress Hosting includes a free standard domain SSL certificate covering the domain name of each WordPress site you add to the server. The server itself is protected by a self-signed SSL certificate to encrypt cPanel, mail, and ftp connections. If you would like to purchase a third-party verified SSL certificate to cover core services on your server, you can find instructions for ordering and installing an SSL certificate for your hostname at Install an SSL certificate on a Domain using cPanel, and you’ll find a guide to installing the certificate at Installing Service SSLs in cPanel. Should you need any assistance purchasing or installing an SSL certificate for the hostname, please feel free to contact a Heroic Support® technician.
  • Delete WordPress Site: The Delete WordPress Site button will completely remove the site and its associated cPanel account, and all data associated with the site immediately will be removed from the server. That data will not be recoverable, so it’s imperative that you confirm that you have a local backup of the site files before deleting any site.
  • Any local backups taken would be stored on the server; these types of backups would be deleted along with the rest of the files in the account if you were to delete the site. It is recommended that any such backups be downloaded to your local computer before you delete a site. Storm® backups, if you elected to configure them during server setup or enabled them later via the Backup tab in your Manage dashboard, do contain a full image of the server and would not be deleted by removing the account; however, restoring an individual file or site from a full-server backup is not a drag-and-drop process and can require significantly more time than restoring from a local backup.

Step #4: Access Your New Site

Once you’ve added the site, an email will automatically be sent to the address on file for your account. The “Welcome to your new WordPress site” email contains:

  • the WordPress site’s login URL
  • the site’s IP address (for adding or updating the domain’s DNS record)
  • instructions for obtaining your free SSL certificate (if it was not able to be installed automatically)
  • SFTP connection information

Once you have made any necessary DNS changes and they have had time to propagate, you should see a standard WordPress installation at the site’s URL. You then can log in and start working with your Managed WordPress site.