Article ID: 113995, created on May 29, 2012, last review on Jun 17, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5
  • Odin Business Automation Standard 4.0
  • Plesk 11.5 for Linux


A Parallels Plesk node is up and running, but it is shown with the status "Not Available" in the Parallels Business Automation - Standard (PBA-S) Panel (Top > Service Director > Plesk Manager > Nodes).


Various issues can cause the above problem, including:

  • Network connectivity issues
  • An expired Plesk license
  • The Plesk admin’s password was changed directly from the Plesk Control Panel
  • The IP Address of the PBA-S node has been changed
  • A broken API-RPC package on Plesk
  • Firewall rules that prevent PBA-S from connecting to the Plesk node


  1. Make sure that Plesk is functioning properly: see more help on Plesk for Linux or Plesk for Windows.

  2. Log into the Plesk Control Panel and check that a valid license is installed.

  3. Make sure that the IP address of the Plesk server is reachable from the PBA-S server and that the connection to port 8443 is not blocked on either the Plesk server or the PBA-S server.

    To check the PBA-S connection, log in on the PBA-S server via SSH. Check the connection of the Plesk server (IP ) on port 8443 with the telnet command:

    # telnet 8443
    Connected to
    Escape character is '^]'.
  4. Get the admin password for Plesk for Linux or Plesk for Windows and update it in PBA-S:

    Top > Service Director > Plesk Manager > Nodes > %Plesk node% > Edit > Plesk administrator password

    This will re-initiate secure keys for further communication. NOTE: The connection may fail because of the Plesk Security Policy.

  5. Run the periodic task "Update Plesk nodes stats info" from the PBA-S Provider Control Panel to update the Plesk node's status:

    Top > Configuration Director > Logging and Errors > Action Log > Task Queue tab > Update Plesk nodes stats info > Run now

    Verify DEBUG PBA-S log for update records. NOTE: The task may fail because of error "PleskAPIInvalidSecretKeyException : Invalid secret key usage. Please check logs for details."

  6. By design, PBA-S communicates with Plesk using the Plesk API. Check the consistency of the API-RPC-related packages on the Plesk server:

    • Linux

    Validate the package psa-api-rpc:

    # rpm -V psa-api-rpc

    The above command will give you a list of missing or modified files, if there are any. If the output is not empty, it most likely means that the package needs to be reinstalled.

    The valid package can be obtained from (according to your Plesk version, OS, and architecture) and reinstalled. The example given below illustrates the installation of the psa-api-rpc package of Plesk 11.5.30 installed on a server with CentOS 6 x64.

    # wget
    # rpm -Uvh --force psa-api-rpc-10.0.0-1.noarch.rpm

    Once the package is reinstalled, run the task "Update Plesk nodes stats info" in PBA-S again, following Step 4 (above).

    • Windows

    There is no simple way to reinstall a single package on Windows. The files in question are located in the %plesk_dir%\admin\plib\api-rpc directory.

    Check that the files in this directory, specifically Agent.php, were not changed after the installation/upgrade, and that they have the correct permissions:

    psaadm: Read, Read&execute
  7. Temporarily disable the firewall on the Plesk node and recheck the node's availability. Make sure that the firewall rules do not disappear after restarting iptables. If it turns out that firewall is the key, please review the firewall rules and modify them so that all the required ports are open.

See also

Plesk node is Not available

Search Words

Plesk node status "Not Available"

Not available

preventive maintenance

not available

poodle plesk error


empty data received from PleskAgent

Plesk node status not available

Plesk server not available

70a5401e8b9354cd1d64d0346f2c4a3e caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 29d1e90fd304f01e6420fbe60f66f838 fc8d1cb26534a6b898faa9daa73bd86e 624ca542e40215e6f1d39170d8e7ec75 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF