Article ID: 126335, created on Jul 26, 2015, last review on Jul 26, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

A Plesk node is in Unavailable status in OBAS.

POODLE hotfix is installed.

Common reasons are not the name of the game.

The error logged in /var/log/hspc/hspc.log on logon attempt from OBAS to Plesk CP unser Top > Service Director > Plesk Manager > Nodes > The Plesk node Name > General Settings > Log in to Plesk is

<errtext>PleskAPIInvalidSecretKeyException : key using is invalid</errtext>

Cause

Routing rules defined on the OBAS server.

In the Plesk database OBAS IP address is set to a certain value, say, 1.2.3.4:

mysql> select * from secret_keys;
+----------------------------------+--------------+-------------+

| key_id                           | ip_address   | description |
+----------------------------------+--------------+-------------+

| ******************************** | 1.2.3.4       | PBAS        |
+----------------------------------+--------------+-------------+

And that is correct

[root@obas ~]# grep SERVER_IP /etc/hspc/hspc.conf
SERVER_IP       = 1.2.3.4

But real connections from OBAS to Plesk go through another IP address, say, 5.6.7.8:

[root@obas ~]# ip route get 1.2.3.4
1.2.3.4 dev venet0  src 5.6.7.8

Resolution

The solution is to review routing rules on OBAS server:

[root@obas ~]# ip route list
...
1.2.3.0/24 dev venet0  scope link  src 5.6.7.8
...

Please be advised that adjusting routing rules is a purely administrative task and is out of scope of Odin support.

As a workaround, it is possible to correct IP address right in the Plesk database so that it looks like:

mysql> select * from secret_keys;
+----------------------------------+--------------+-------------+

| key_id                           | ip_address   | description |
+----------------------------------+--------------+-------------+

| ******************************** | 5.6.7.8      | PBAS        |
+----------------------------------+--------------+-------------+

Search Words

Plesk node status not available

<errtext>PleskAPIInvalidSecretKeyException : key using is invalid</errtext>

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF