Search Engine: Elastic

Article ID: 131076, created on Jun 27, 2017, last review on Jun 27, 2017

  • Applies to:
  • Operations Automation 7.1

Symptoms

  1. The task "Plesk in VPS 101: register domain" fails with error:

    https://203.0.113.2:8443/enterprise/control/agent.php : protocol misconfiguration
    
  2. Log of OA (/var/log/pa/core.log or /var/log/poa.log) shows that the error is returned as a result of the following API:

    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <packet version="1.4.0.0">
      <domain>
        <get>
          <filter>
            <client_id>2</client_id>
          </filter>
          <dataset>
            <gen_info></gen_info>
          </dataset>
        </get>
      </domain>
    </packet>
    
  3. Domain owner on Plesk side has the different ID (from Plesk's DB):

    mysql> select cl_id from domains where name = 'example.com';
    +-------+
    | cl_id |
    +-------+
    |     5 |
    +-------+
    1 row in set (0.00 sec)
    

Cause

IDs of Plesk customer in OA and Plesk are different.

OA requests from Plesk the list of domain belonging to non existent customer and receives nothing. As a result the task fails.

Resolution

Contact Odin Technical Support to synchronize IDs.

Additional Info

The similar error may also be caused by desynchronization of domain's ID. See also "Plesk related task fails: protocol misconfiguration" .

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF