Plesk Multi Server task error: Unable to find certificate Domain example.com

Symptoms

• In the Tasks section the following errors may be seen:
  

  PLESK_INFO: Webspace does not exist

  or

  PLESK_INFO: Unable to find certificate Domain example.com

• Affected domains are not clickable in Domains section. These domains are edited from the Plesk user interface in the Subscriptions that they belong to only.
• Let's Encrypt certificate is installed for the domain.
• The following error can be found in /usr/local/psa/admin/panel.log:
  

  CONFIG_TEXT: ERR [extension/plesk-multi-server] Task run failed with message 'Unable to find certificate Domain example.com'

Cause

Corrupted mapping, that is caused by the Plesk bug #EXTPMS-1355 which will be fixed in one of the future Plesk updates.

Resolution

Restore mapping for these domains using the following way:

1. Connect to the server using SSH.
2. Make the  backup of sqlite database:
   

   # cp /usr/local/psa/var/modules/plesk-multi-server/plesk-multi-server.sqlite3 /usr/local/psa/var/modules/plesk-multi-server/support-backup-<date>-plesk-multi-server.sqlite3

3. Updated the status of the last Failed (status=4) task to Complete (status=3). Id is shown at the Tasks section:
   

   # sqlite3 /usr/local/psa/var/modules/plesk-multi-server/plesk-multi-server.sqlite3
   update tasks set status=3 where id=110180;

4. Find out id of the domain, of the subscriptions domain belongs to, guid of the Subscription on the Master Node:
   
   • Log in to psa database:
     

     # plesk db

   • Find out id of the domain, id of the subscription and guid:
     

     MYSQL_LIN: mysql> select id, webspace_id, guid from domains where name="example.com";
     +----+------------+-----------------------------------------------+
     | id | webspace_id|    guid                                       |
     +----+------------+-----------------------------------------------+
     | 328|        218 | c68171eb-6751-4004-83d4-7345a57fc494          |
     +----+------------+-----------------------------------------------+
     1 row in set (0.00 sec)

5. Find out id and guid of this domain on the Service Node as well:
   
   • Log in to psa database on the Service Node:
     

     # plesk db

   • Find out id of the domain and guid:
     

     MYSQL_LIN: mysql> select id, guid from domains where name="example.com";
     +----+--------------------------------------+
     | id | guid                                 |
     +----+--------------------------------------+
     | 42 | d4f9d595-1add-471d-8b4f-fc7fcceb9d07 |
     +----+--------------------------------------+
     1 row in set (0.00 sec)

6. Using webspace_id from the 3d step it is required to look for id of the subscription in the sqlite "subscriptions" table and id of the Service Node.
   
   • Log in to the sqlite database:
     

     # sqlite3 /usr/local/psa/var/modules/plesk-multi-server/plesk-multi-server.sqlite3

   • Find id of the subdcription:
     

     MYSQL_LIN: sqlite> .headers on
     sqlite> .mode line
     sqlite> select id, slaveNodeId from subscriptions where masterId=218;
     id = 26
     slaveNodeId = 2

7. When all required details are collected, mapping may be restored with the following command:
   

   MYSQL_LIN: sqlite> insert into sites (slaveNodeId, masterId, slaveId, masterGuid, slaveGuid, subscriptionId, name) values (2, 328, 42, "c68171eb-6751-4004-83d4-7345a57fc494", "d4f9d595-1add-471d-8b4f-fc7fcceb9d07", 26, "example.com");

   Where:

   slaveNodeId and subscriptionId - slaveNodeId and id of the subscription from "subscriptions" table (step 5);
   masterId and masterGuid - id and guid from the Master Node (step 3);
   slaveId and slaveGuid - id and guid from the Service Node (step 4);
   name - deomain's name.
   

   Note: Consider changing the values in the 6th step's command with the appropriate one, that suit values from the database.

8. If the domain also had Webspace does not exist error, fix it with the same way it is described in the 1st step, but change ID to the latest failed task with the Webspace does not exist error instead.