Article ID: 113727, created on Apr 19, 2012, last review on Aug 12, 2014

  • Applies to:
  • Plesk
  • Plesk Expand


I cannot connect to a Parallels Plesk Panel (PP) 8 server via the Parallels Plesk Expand (PPE) control panel.
When trying to log in, I receive the following error:
Cannot open Plesk Server window because Plesk API RPC is not installed on the Plesk Server. Contact your system administrator for support.
While trying to diagnose the problem, I delete the server from PPE, and when trying to add it back, I get the following error:
The specified Plesk server has no PSA API software installed or the installed software is outdated. Please refer to your Plesk Installation Manual to learn how to install/upgrade your PSA API software.
The psa-api-rpc package is installed on the server, so the above error messages are not accurate:
# rpm -qa psa-api-rpc


The installation of the psa-api-rpc package is probably missing the agent.php file. You may check whether this is the case by using this command, e.g.:
# rpm -V psa-api-rpc-8.6.0-rhel4.build86080930.03
missing /usr/local/psa/admin/htdocs/enterprise/control/agent.php

The file may have been deleted in order to eliminate a vulnerability in PP; however, this is not a recommended solution. It is necessary to install Micro-Updates in order to properly protect the server from vulnerabilities.


In order to fix the psa-api-rpc package and install all Micro-Updates, the following steps should be executed on the server where PP is installed:
1) Download the appropriate psa-api-rpc package for PP 8.6 for Windows, depending on your OS/architecture, here:

Example link for RHEL 4 32-bit:

2) Reinstall the package using the following command:
# rpm -Uvh --force <FILE_NAME.rpm>

(Replace "FILE_NAME" with the name of the downloaded file.)

3) Install all Micro-Updates using this command:
# /usr/loca/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base

Note: If you are running a very old operating system version, you may encounter this issue:

113724 Cannot update Autoinstaller to the latest version


a914db3fdc7a53ddcfd1b2db8f5a1b9c 8760abb54be64bdc3c8805b6572624e8 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF