Logging into Plesk
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.
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.
CentOS Linux 7 will reach its end of life (EOL) on June 30, 2024. Learn what you need to know and how to prepare ahead of time in anticipation of the CentOS 7 EOL date.
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.
Learn to configure WHM to send backups to Amazon S3. Seamlessly manage your off-server backups for your site’s security and data protection.
Automate your server tasks easily. Learn how to create, schedule, and manage Cron Jobs in cPanel without the risk of command-line syntax errors.
Secure your server using the Principle of Least Privilege (PoLP). Learn how restricting user access prevents malware and how to manage file permissions.
In cPanel, each MySQL database can have multiple users. If needed, you can delete a user from a specific database or remove the MySQL user entirely from your account. This can be done directly from the database or through your cPanel account.
Protect your server by reverting unwanted changes. Learn how to safely restore your CSF firewall configuration from a backup in WHM’s Firewall Profiles.
Secure your cPanel account with Two-Factor Authentication (2FA). Learn how to set up and configure 2FA using Google Authenticator or Duo Mobile.
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.
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.