Changing MySQL User Password Using WHM/cPanel

This is the recommended method when performing a MySQL user password change when your server contains a cPanel installation.

1. Login to your WHM/cPanel and search for “Change MySQL® User Password“.

   

2. Select the MySQL user you wish to change the password.
3. Ensure to type a password with a strength score of at least 80%, as shown below and press the “Change Password” once completed.

Changing MySQL User Password Using the Command Line Interface 

The following steps will describe the process involved in changing the MySQL user password via the command line once you’ve logged into your server via SSH or by using the Console feature in the customer portal.

1. Login to the server as the “root” user.
2. Type the command mysql -u root -h localhost -p to login to MySQL as the “root” user.
3. Enter the “root” user MySQL password to login.
   1. If you are unsure of what the “root” user password is, you can use the command my_print_defaults -s client to view it in the main command prompt.
4. Now that you are logged in to MySQL as “root” user.

   

5. Run command SELECT user FROM mysql.user; to view a full list of available users.

   

6. Use the following command to alter the password ALTER USER ‘pascalsuissa’@’localhost’ IDENTIFIED BY ‘MyNewPasswordis1234!’;
   1. “pascalsuissa” is the username.
   2. “MyNewPasswordis1234” is the password.

7. Once the command has completed running, the prompt will display a “Query OK” message, indicating that the password change is now complete.

   

The post Resetting MySQL User Password appeared first on Hivelocity Hosting.

cPanel simplifies the backup process with its built-in backup configuration feature. This tool lets administrators schedule automated backups, set retention periods, and select specific files, databases, or entire accounts for backup. As a result, it offers flexible backup management, tailored to the unique needs of each server. Moreover, administrators can easily choose storage locations, whether locally or via remote destinations such as FTP, Amazon S3, or Google Drive.

A reliable backup strategy is vital for disaster recovery and business continuity. With the right setup, you can quickly restore services after data loss, minimizing downtime and preventing data compromise. This WHM/cPanel Backup guide will go over the best backup practices, 3-2-1 backup rule, the ideal backup layout in your server, and backup configuration options within WHM/cPanel.

Best Backup Practices

When managing backups in WHM and in general, following best practices ensures data protection and smooth recovery in case of emergencies. By following these best practices, you ensure that your WHM backups and overall backup strategy provide strong protection against data loss and enable quick recovery in case of failure.

1. Schedule Regular Backups: Regular backups are essential to safeguard your data. In WHM, configure automated daily, weekly, or monthly backups to keep your server data up to date. This reduces the risk of losing critical information due to unexpected events. Make sure the frequency aligns with your business needs to avoid large gaps between backups.
2. Store Backups in Multiple Locations: Relying solely on local backups can be risky. Use WHM’s options to send backups to remote destinations like FTP, Amazon S3, or Google Drive. Storing backups both locally and remotely ensures that if one storage option fails, you still have a secure copy elsewhere
3. Use Incremental Backups: WHM offers an incremental backup option, which only saves changes made since the last backup. This method saves storage space and speeds up the backup process. Incremental backups are ideal for large servers where full backups may take too long or consume too much space.
4. Implement Retention Policies: Set up retention policies to keep a specific number of backup copies. This practice ensures that older backups are automatically deleted when they’re no longer needed, freeing up storage space and reducing costs. Be mindful of keeping enough backups to cover potential data loss scenarios.
5. Monitor Backup Processes: Keep a close eye on your backup processes through WHM’s backup logs and notifications. Monitoring helps you identify issues such as failed backups or insufficient storage space. Addressing these issues promptly ensures your backups remain reliable.

3-2-1 Backup Rule

The 3-2-1 backup rule is a widely recommended strategy for ensuring data protection and recovery. Following the 3-2-1 rule enhances data security and ensures that you can quickly recover your information in the event of data loss.

1. Three Copies of Your Data: Keep at least three total copies of your data. This includes the original data and two backups. Having multiple copies reduces the risk of data loss from hardware failures or corruption.
2. Two Different Media Types: Store the backups on at least two different types of storage media. For example, you might use an external hard drive and a cloud storage service. This diversification helps protect against failures specific to one medium, such as a hard drive crash.
3. One Offsite Backup: Keep at least one backup offsite to protect against local disasters such as fires, floods, or theft. This could be a cloud backup or a physical backup stored at a different location. Offsite backups ensure your data remains safe even in catastrophic scenarios.

Designing the Ideal Server Backup Layout

When designing the ideal server backup layout, it’s essential to consider how to organize backups across different partitions and types of drives. Proper partitioning and selecting the right storage media for your backups can significantly improve performance, reliability, and recovery times.

Partitioning for Backup Layout

• Create a dedicated partition solely for storing backups. This ensures that backups do not interfere with the system’s primary operations or other partitions, preventing scenarios where filling up the root or home partitions could crash the system.
• It’s best practice to keep the operating system, application data, and backup data on separate partitions. For example:
  • / for the operating system.
  • /var or /home for application and user data.
  • /backup (or another designated partition) for backups

Choosing the Right Storage Media

The type of drive you use for storing backups is critical in determining how fast you can back up and restore data, as well as the long-term reliability of the storage.

• Hard Disk Drives (HDDs): Cost-effective and high-capacity, HDDs are suitable for local backups that don’t require rapid access. Use them for less frequent backups, such as weekly full backups, stored on a dedicated partition to avoid impacting system performance.
• Solid-State Drives (SSDs): SSDs offer faster read/write speeds, making them ideal for critical backups that need quick recovery, like daily or incremental backups. Create a separate SSD partition to enhance access speed and reliability for frequently used backup data.

NVMe drives, while fast, are not ideal for backup storage due to their high cost per gigabyte and lower write endurance, leading to faster wear from frequent backups. Their speed is often unnecessary for backup tasks, where traditional HDDs or SATA SSDs suffice. Additionally, NVMe drives generate more heat and offer fewer cost-effective redundancy options.

WHM/cPanel Backup Configuration

The WHM/cPanel Backup Configuration feature simplifies automated backups, allowing users to schedule, customize, and store data locally or remotely for secure, reliable recovery. WHM backups involve all accounts and are server-wide while cPanel backups are backups within specific accounts. We will review both and provide procedures accordingly below.

WHM Backups (All Accounts/Server-Wide)

Backup Status & Type

1. Access the feature by navigating to Home / Backup / Backup Configuration within WHM.
2. Proceed to check the box for “Enable Backups”.
3. Select a backup type. For starters it is good to go with the default “Compressed” option.
   1. Compressed: This option saves disk space by compressing the backup but takes longer to create. It’s ideal when storage space is limited and backup speed is not critical.
   2. Uncompressed: Backups take more space but are created faster. This option is useful when you need quicker backups and have enough storage space available
   3. Incremental: Only backs up changes since the last backup, saving both time and disk space. It’s the most efficient option for ongoing backups, especially in environments with frequent changes.

      

Available Disk Space Check & Timeout Values

1. Check the “Check the Available Disk Space” option and set it to 10% so that if the available disk space is less than the amount that you specified, the system will not run the backup.
2. Leave the values for “Maximum Destination Backup Timeout” and “Maximum Backup Restoration Timeout” untouched.
3. The default scheduling and retention section value is of course to have “Daily Backup” checked along with all the days you wish to backup but that can be modified as needed along with adding a weekly or monthly backups if dailies are not a good fit. 

   

Files Settings

1. “Back up User Accounts” should be checked with access logs and bandwidth Data” both checked. The option to “Back up Suspended Accounts” is also available but not checked by default.
2. Ensure to have “Back up System Files” checked to support server restoration.

   

Databases 

1. Select the “Databases” option works best for you, however, the default and most recommended is to select “Per Account Only”.
   1. Per Account Only: Use the “mysqldump” command to create backup files with the “.sql” file extension for each account.
   2. Entire Data Directory: Back up all files in the “/var/lib/mysql/” directory.
   3. Per Account and Entire Data Directory: Back up all files in the “/var/lib/mysql/” directory, and use the “mysqldump” command to create backup files with the “.sql” extension for each account.

      
      

      

Backup & Retention Directories

1. Configure the backup path under the “Configure the Backup Directory” section to match the directory/mounting point of your designated backup location. For example, if my partition is mounted to the /backup directory, then /backup is what will go into that field. 
2. Backup Staging Directory can be set to the same path as your regular backups, however, that can be changed if necessary based on your preference, partition layout, and storage conditions.
3. Ensure to check the “Retain Backups in the Default Backup Directory” so that once backups are made and the system transfers the backups to another destination it will maintain the backups in the default directory. If you disable this option, the system will delete the backups after they move to another destination.

4. By default, the “Mount Backup Drive as Needed” is unchecked but can be checked if you’re experiencing any issues with the mounting point not mounting properly. Note that this requires a separate drive or other mount point.

   

Additional Destinations

WHM Backups can be sent to another location off server if needed. This can be useful if you do not wish to store backups locally on the server. 

1. Proceed to the “Additional Destinations” tab within “Home / Backup / Backup Configuration” at WHM. 
2. There are multiple options for backing up the account externally as shown in the image below.

   

3. Information about the different types of Remote Backup Destinations and how to configure them can be found in the official cPanel documentation as that is a live document that should be examined upon configuration of that section. 

cPanel Backups (Specific cPanel Accounts)

A cPanel account backup creates a complete copy of your website files, databases, and emails, ensuring easy recovery and data protection in case of issues. This section is more specific to clients accessing their cPanel accounts as they would not normally have access to the WHM section unless they are the owner of the server/have access to the root user.

1. The cPanel backup section can be reached by entering your cPanel account and navigating to “Backup” under the “Files” section.

   

2. Within the section you can download a zipped copy of your entire site or a part of your site that you can save to your computer. When you backup your website, you have an extra copy of your information in case something happens to your host. The following can be made as well within the feature.
   1. A full backup which will create an archive of all of your website’s files and configuration. You can use this file to move your account to another server or to keep a local copy of your files.
   2. Account backups by date as per available backups on server.
3. Partial Backups are also available along with the ability to restore them. The available items are listed below for reference.
   1. Home Directory Backup.
   2. Database Backup.
   3. Email Forwarders.
   4. Email Filters.

      

Further Assistance

For any further assistance involving partitions and backup configuration in WHM, do not hesitate to reach out to the Hivelocity Support team via a chat, support ticket, or phone at 888-869-4678.

The post WHM/cPanel Backup Guide appeared first on Hivelocity Hosting.

The post How to change the root password from WHM appeared first on Hivelocity Hosting.

MX records, or mail exchange records, are special server settings that help control the way your email is routed. In terms of DNS, an MX record tells incoming mail which server can receive it, and then directs it to that server. In other words, if your MX records are pointing to the wrong location, you won’t be able to receive emails.

Most web hosts create DNS records for their clients that default to the host’s server. If you’d like to use a different mail provider separate from your hosting account, you need to create an MX record.

*Note: changing your MX records only points newly incoming mail to your updated email server. This means that any emails already on your existing mail server will not be transferred over.

Understanding the Structure of an MX Record

MX records use two important pieces of information when directing traffic: a priority number and the domain name where the server is hosted.

The priority number determines which order a server will receive mail in and starts with the lowest available priority, starting with “0”. If two servers with the same priority level are both available, one will be chosen at random.

The second part, the domain name, is the name of the specific mail server the mail is being sent to. They typically look something like “mail.DOMAIN.com“. Some hosting providers have special instructions for setting up MX records and may also require a “.” placed at the end of the server name, such as “mail.DOMAIN.com.“.

Configuring MX Records for Gmail

As Gmail is one of the most popular email providers, for the sake of this tutorial, we’ll focus on how to create MX records using Google’s default mail servers.

Google provides users with five different mail servers, assigning each a default priority level. They are:

• ASPMX.L.GOOGLE.COM -> Priority 1
• ALT1.ASPMX.L.GOOGLE.COM -> Priority 5
• ALT2.ASPMX.L.GOOGLE.COM -> Priority 5
• ALT3.ASPMX.L.GOOGLE.COM -> Priority 10
• ALT4.ASPMX.L.GOOGLE.COM -> Priority 10

Using the default priority settings, your mail will be routed to the first available server with the lowest priority level. In most instances, this will be ASPMX.L.GOOGLE.COM, since it has a priority level of 1.

If however, the first server is unavailable for some reason, then mail will be routed to the next available server. Since both ALT1 and ALT2 carry the same priority level, it will be sent to one of them at random.

More information on Google’s mail server’s can be found on their official support page.

Now that you know what the names for Google’s servers, you can set up the MX records for them using your favorite control panel.

Changing an MX Record Using cPanel

To setup or make changes to your MX records using cPanel, follow these steps:

1. First, you’ll need to log in to your cPanel account using your username and password. You can access your control panel by using https://www.YOURDOMAIN.com:2082.
2. Next, in the Mail section of your dashboard, click on the icon for Modify Mail Exchanger (MX Entry).
   
3. Click the option to Change an MX Entry.
4. Select the domain from the drop-down menu.
5. If you’re using Gmail, then in the section labelled Add New Record, enter the server information listed above.
6. Set the priority number for each record, remembering that lower numbers have higher priority.
7. In the Destination box, enter the name/domain of the new mail server. If using Gmail, start with:

   ASPMX.L.GOOGLE.COM

   repeat for the other servers on the list.

8. When you’ve finished making changes to the MX record, you can click Add New Record to save your changes.

*Note: it may take upwards of 48 hours for the DNS propagation to take effect.

If should ever want to delete an MX entry using cPanel, you can do so simply by clicking the Delete button next to the applicable MX record and confirming your selection.

Changing an MX Record Using WHM (Web Host Manager)

To setup or make changes to MX records using WHM, follow these steps:

1. First, log in to your WHM account using your username and password.
2. On the left-hand side, locate and click on the option for DNS Functions.
3. Click on Edit DNS Zone.
4. From the drop-down window, select your domain and click Edit.
5. If there is already an existing MX record entered, you should delete it.
6. Enter your domain name and leave the second box as is.
7. From the drop-down menu, select the option for MX.
8. If you’re using Gmail, then enter the information for Google’s mail servers as listed above, including the trailing period. For example:

   ASPMX.L.GOOGLE.COM.

9. When you’re finished editing the records, click Save.

Keep in mind, it may take a day or so for your DNS changes to be updated.

Changing an MX Record Using Plesk

To setup or change an MX record using the Plesk control panel, follow these steps:

1. First, you’ll need to log in to Plesk using your username and password.
2. Under the Websites & Domains tab, select DNS Settings.
3. Locate the domain you are making changes to and click the option to Manage.
4. Select the option to Add a Record.
5. Using the drop-down menu, change Record type to MX.
6. Leave the option for Mail domain blank.
7. In the form field labelled Mail exchange server, enter the name of the mail server you are sending your incoming mail to. If you are using Gmail, start with the first mail server:

   ASPMX.L.GOOGLE.COM
   

8. Using the drop-down menu labelled Specify the priority of the mail exchange server, enter the priority number for the server as listed above. If you do not have a specific priority number for the mail server you’re using, leave it set on “0“.
9. Click on Apply to save your changes and repeat for any additional MX records you need to create.

Remember that changes to DNS won’t take effect immediately.

And there you have it! You should now be able to modify an MX record for Gmail using any one of the above control panels.

Popular Links

Looking for more information on MX Records? Search our Knowledge Base!

Interested in more articles about Web Hosting? Navigate to our Categories page using the bar on the left or check out these popular articles:

• DNS Configuration: Everything You Need to Know
• What is Cron Job?
• How to Resolve Error 421 Service Not Available and Other Issues with FTP Service

Popular tags within this category include: DNS, FTP, IIS, MX Records, and more.

Don’t see what you’re looking for? Use the search bar at the top to search our entire Knowledge Base.

The Hivelocity Difference

Seeking a better Dedicated Server solution? In the market for Private Cloud or Colocation services? Check out Hivelocity’s extensive list of products for great deals and offers.

With best-in-class customer service, affordable pricing, a wide-range of fully-customizable options, and a network like no other, Hivelocity is the hosting solution you’ve been waiting for.

Unsure which of our services is best for your particular needs? Call or live chat with one of our sales agents today and see the difference Hivelocity can make for you.

The post How to Configure an MX Record appeared first on Hivelocity Hosting.

a. Check WHM >> Server Configuration >> Tweak Settings and disable the following options :

*Prevent users from parking/adding on common internet domains. (i.e. hotmail.com, aol.com)

*Allow cPanel users to reset their password via email

*Default catch-all/default address behavior for new accounts – fail

b. Then goto WHM >> Security >> Manage Wheel Group Users

* Remove all the users present in the “Manage Wheel Group Users” section except the root and your

account from the wheel group.

c. Select WHM >> Service Configuration >> FTP Configuration

*And Disable Anonymous FTP

d. Select WHM >> Account Functions >> Manage Shell Access

* Disable the Shell Access for all the users if there is no need to enable it.

e. Select WHM >> SQL Services >> MySQL Root Password

Then change the root password for MySQL

Perform Quick Security Scan for Trojan Horses from your WHM >> Security in a week.

The last but not the least, important security for your server , when you are creating any new reseller account, Select WHM >> Resellers >> Reseller Center

Disable the “Allow Creation of Packages with Shell Access” and always enable “Prevent Accounts from being created with shell access” it will not allow third party to access your server without your permission.

The post How to secure your server via WHM? appeared first on Hivelocity Hosting.

The post How to assign free IP address to the server? appeared first on Hivelocity Hosting.

Now you know how to backup the system configuration files of your dedicated hosting server via WHM Backup Feature.

The post Backup System Configuration Files Using WHM backup Feature appeared first on Hivelocity Hosting.

2) On the main Screen Find the Backup and simply click on it.

3) Click the Configure Backup icon

4) It will show you various options with frequency that backup run and can be configured on this page.

Configure Backup Options:

Backup Status:

Backup Interval:

Backup Retention:

Days to Run Backup:

Remount/UnmountBackup Drive:

BailOut If Backup DriveMountFails:

Incremental Backup:

Backup Accounts:

Backup Configuration Files:

Backup SQL Databases:

Backup Access Logs:

Backup Type:

Remote FTP Host:

FTP Backup User:

FTP Backup Password:

FTP Backup Directory:

FTP Backup Passive Mode:

Backup Destination:

Select Specific Users:

5) Simply, “Enabled” the “Backup Status” and change the settings as per your requirements and hit the “Save” button.

The post Enable Backup in WHM / cPanel Dedicated Servers appeared first on Hivelocity Hosting.

2) Click on to the “Account Functions” listed on the left sidebar.

3) Now, click on the “Create a new account” option. Once you click it fill all the required fields and click on the “Create” button on the top. You will get the account information of the recently created account.

The post How to Create a new (add website) Hosting Account in WHM? appeared first on Hivelocity Hosting.

2) Once you click onto “Account Functions” to get options.

3) You will see an option “Limit Bandwidth Usage”. Click on it and select the domain for which you want to set or increase a specific amount of bandwidth limit. Allocate the amount of bandwidth and click on the “Change” button.

The post How to manage the bandwidth of an account in WHM? appeared first on Hivelocity Hosting.

2) Now click on the “Quota Modification” option under the accounts functions section.

3) Select a domain to which you want to increase the amount of disk space. Allocate the amount and hit the button.

The post How to Manage the Disk space of an Account in WHM? appeared first on Hivelocity Hosting.