Symptoms

  1. Task Provisioning "WebSpace" for APS application WebHosting Plesk failed with error like:

    APS Application Error:
500 Internal Server Error
[ApplicationUnknownError] Error occurred during request to WHP API on service node 192.168.1.100: " p123.webspace.tld. ."..

Body: {
"code": 500,
"message": "Error occurred during request to WHP API on service node 192.168.151.1: \" p123.webspace.tld. .\".",
"type": "WhpApiException",
"details":
{
"errorCode": 0,
"error": "PmShm.Sdk.Exception",
"info": null
},
"error": "ApplicationUnknownError",
"http_request": "POST /web/WebSpace"
}

  2. Error like below appears in requests.log on WebHostingPlesk Website Manager node:

    [2018-03-04 14:30:04] whp_requests.INFO: Execution context [POST https://192.168.1.2:6301/web/WebSpace (ID: 9c2d5626e9ecf7e2acec5848e7f0ea628414089f)]
#Response received from WHP (Finished in 0.085875 s):
HTTP/1.1 500 Internal Server Error
["Server: sw-cp-server","Date: Sun, 04 Mar 2018 11:30:04 GMT","Content-Type: application\/json","Connection: close"]
{
    "status": "error",
    "errorMessage": "\u041d\u0435\u0432\u0435\u0440\u043d\u043e\u0435 \u0438\u043c\u044f p123.webspace.tld. \u0422\u0430\u043a\u043e\u0439 \u0434\u043e\u043c\u0435\u043d \u0443\u0436\u0435 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u0435\u0442.",
    "details": {
        "errorCode": 0,
        "error": "PmShm.Sdk.Exception",
        "info": null
    }
}

    Converted errorMessage: Неверное имяp123.webspace.tldТакой домен уже существует.

  3. There are 2 webspaces with same Technical name under PCP > Services > WebHostingPlesk > Webspaces.

Cause

Algorithm for generation for technical names for webspaces was changed in Odin Automation 7.3 (related to WEBSPACE_ID placeholder). It generates unique IDs for webspaces, but these ids sometimes can match with previously generated names in Odin Automation 7.1 or Odin Automation 7.2.

Resolution

The issue should not affected new Odin Automation 7.3 with installed WebHostingPlesk module. Affected subscriptions could not be fixed without assistance from Developers (source code modifications are required). Please, submit SME/Dev-OA ticket to fix similar issues.

Internal content