Control Panel

  1. 2 min read

    Log into Plesk via your Liquid Web account by selecting your server and clicking “Go to Plesk.” Use your server credentials to log in or access Plesk directly at https://yourIP:8443.

  2. 2 min read

    File Manager in Plesk is great for uploading individual files or compressed files to your domain. It could take a longer time to upload than FTPS, but you can access File Manager anywhere you have an internet connection without having to download FTPS software to your computer.

  3. 2 min read

    Creating scheduled tasks via a crontab file automates script execution on your server. While you can manually edit the crontab, using cPanel simplifies the process. It allows setting preferences, entering commands, and receiving email updates upon execution, minimizing syntax errors and ensuring smooth operation.

  4. 2 min read

    Least Privilege, or the Principle of Least Privilege (PoLP), ensures that each process, user, or program accesses only the information and resources essential for its purpose. This helps in setting server permissions, granting users and processes only the necessary functions to complete their tasks, without accessing other files and programs.

  5. 2 min read

    Two-factor authorization means that instead of just a password, you will also need a rotating authentication token along with the password (two factors) to log into your cPanel account. Only the correct combination of the first and second factor will allow you to log in and access your account. In order to require cPanel user two-factor authentication, you need to set it up in WHM to be enabled for all users.

  6. 3 min read

    To secure customer information on your website, enabling the AutoSSL feature in WHM is a recent and convenient option. AutoSSL lets you apply SSL certificates to any domain on your server, supporting up to 200 sites for free.

  7. 5 min read

    The PHP Memory_Limit defines how much memory a process can use on your server. When a client request initiates a PHP process, exceeding this limit causes the process to fail, resulting in an HTTP 500 error reported by Apache.