Plesk tasks fail: 'PleskAPIInvalidSecretKeyException: key is not found'

Created:

2016-11-16 12:48:52 UTC

Modified:

2017-08-16 16:07:08 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Plesk tasks fail: 'PleskAPIInvalidSecretKeyException: key is not found'

Applicable to:

  • Plesk for Linux

Symptoms

A customer cannot properly manage their VPS with Plesk subscription in OA due to various problems described below.

  1. The customer added domain in OA Customer CP and assigned Plesk Panel hosting on it. All provisioning tasks completed in OA, however the domain was not added to Plesk and its status in OA CCP is 'Not in sync/Adding' :

    Your text to link here...

  2. Plesk license cannot be installed in the VPS through the BA Control Panel with the following error appearing in the corresponding OA background task execution output:

    PleskAPIInvalidSecretKeyException : key is not found

The same error message is displayed in OA Customer Control Panel like on the screenshot:

Cause

Secret key is missing in Plesk database, while it is present in OA database.

OA database:

plesk=> SELECT key FROM psa WHERE sub_id=<SUB_ID>;
host_id | key
---------+----------------------------------
28 | 666fec857fec542304c943bf11069bc2

(1 row)

(on OA >= 6.0 this is replaced by akey field)

Plesk database:

mysql> SELECT * FROM secret_keys;
Empty set (0.00 sec)

Secret key is used for authorization between OA and Plesk Panel. If the secret key is lost in Plesk then OA cannot perform provisioning operations in Plesk.

Resolution

Perform the following actions to resolve the problem:

  • Remove data about secret key from OA database for the particular subscription in question:

    plesk=> UPDATE psa SET key = NULL WHERE sub_id = <SUB_ID>;

    Replace the <SUB_ID> in the SQL query above with the ID of the subscription in question.

    Note : OA >=6.0 uses akey column.

  • Reinitialize Plesk in OA Customer Control Panel

  • Wait until all re-configuration tasks are completed in OA Task Manager for the problem VPS with Plesk. As a result secret key will be regenerated and problem must be solved.

  • Resubmit domain to the Plesk Panel server in OA Customer CP, try to install Plesk license once again in PBA.

Have more questions? Submit a request
Please sign in to leave a comment.