• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Why is Plesk 10.1 and the latest API not in sync with each others features?

E

eli007

Guest
I'm getting frustrated with the lack of support people are getting with the Plesk API


I have a few questions and concerns that I hope someone will be kind enough to answer.

Why is it that in the Control Panel when making a new sub domain the domain is made in the root folder with full read/write permissions but when a sub domain is created using the API the subdomain is created in /subdomains folder with NO read/write capabilities OR the correct folder structure used by the Control Panel when a sub domain is created thru it.

subdomain created via API with permissions
------------------------------
Code:
/subdomains/ - fle (0755)
    | test - fle (0755)   
        | conf - 0750
        | error_docs - 0750
        | cgi-bin - flcdmpe (0750)
subdomains created via Control Panel with permissions
------------------------------------------
Code:
/test/ - flcdmpe (0750)
    | mt_images - flcdmpe (0755)
    | index.html - adfrw (0755)
There is a big difference in folder contents and permissions
 
Back
Top