Troubleshooting Common Plesk Issues on Linux

This section outlines procedures for resolving the most frequent challenges encountered when operating Plesk on Linux environments. Specifically, it provides essential guidance if you encounter any of the following:

• Inability to reach the Plesk login page.
• Difficulties logging into the Plesk interface.
• Loss of the administrator's password.
• Operational problems when Plesk is deployed within a Virtuozzo container.

Should your specific issue not be addressed within this guide, or if the suggested solutions do not resolve your problem, we encourage you to visit the official Plesk Knowledge Base or to contact our dedicated technical support department for further assistance.

Resolving Plesk Access Issues

When attempting to access Plesk, you might encounter error messages such as "Unable to initialize session", "Domain ID is undefined", or "Client ID is undefined". These indicators typically point to Plesk's inability to establish a session, often due to a lack of available disk space in the $PRODUCT_ROOT_D/admin/sessions directory.

Insufficient free disk space on the Plesk server is a common underlying cause for these session initialization failures. To diagnose this, it is crucial to verify the current disk space utilization. You can do this by executing the following commands in your server's terminal:

df -h
du -h /var/log/

If disk space usage is reported at or near 100%, it is imperative to free up space. This can be achieved by identifying and removing unnecessary files or by implementing proper log file rotation, particularly within the /var/log/ directory. For comprehensive instructions on managing and rotating log files, please refer to the section on Log Rotation in the Plesk advanced administration guide.

Troubleshooting Plesk Login Problems

If you receive the error message "Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied." when attempting to log in, it signifies that Plesk's configured IP access policy is preventing access from your current IP address.

To regain access to Plesk from a restricted IP address, you will need to modify the server's database settings. Follow these steps carefully:

1. Log in to the server via SSH: Establish an SSH connection to your Plesk server using a user with appropriate privileges (e.g., root).
2. Modify the IP access policy in the psa database: Once logged in, you will need to interact with the Plesk database (psa) to adjust the access policy.

To identify the currently enforced access policy, including any restricted or allowed IP addresses, execute the following commands within the MySQL client:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
mysql> select * from cp_access;
mysql> select * from misc where param='access_policy';

To clear the existing IP access policy settings, effectively removing all current restrictions, you can delete all records from the cp_access table. This action will reset the access policy to its default, allowing access from any IP address unless further restrictions are configured.

mysql> delete from cp_access;
mysql> update misc set val='default' where param='access_policy';

After clearing the policy, you should be able to log in. It is recommended to then review and reconfigure your IP access policy within the Plesk control panel if specific access restrictions are desired for security purposes.