• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Problems adding a subdomain with API

I

inxenio

Guest
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

- Windows 2008 Server R2 x64
- Plesk 10.1.1

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE

Try to add a subdomain with API...
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<packet version="1.6.3.0">
<subdomain>
<add>
<parent>testdomain.com</parent>
<name>subdomainname</name>
<home>/site1</home>
</add>
</subdomain>
</packet>

I receive the confirmation:

<packet version="1.6.3.0"><subdomain><add><result><status>ok</status><id>35</id></result></add></subdomain></packet>

ACTUAL RESULT

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.3.0">
<subdomain>
<get>
<result>
<status>ok</status>
<filter-id>testdomain.com</filter-id>
<id>35</id>
<data>
<parent>testdomain.com</parent>
<name>subdomainname.testdomain.com</name>
<property>
<name>fp</name>
<value>false</value>
</property>
<property>
<name>fp_auth</name>
<value>false</value>
</property>
<property>
<name>asp</name>
<value>true</value>
</property>
<property>
<name>asp_dot_net</name>
<value>true</value>
</property>
<property>
<name>managed_runtime_version</name>
<value></value>
</property>
<property>
<name>ssi</name>
<value>true</value>
</property>
<property>
<name>ssi_html</name>
<value>false</value>
</property>
<property>
<name>php</name>
<value>true</value>
</property>
<property>
<name>php_version</name>
<value></value>
</property>
<property>
<name>php_handler_type</name>
<value>cgi</value>
</property>
<property>
<name>cgi</name>
<value>true</value>
</property>
<property>
<name>perl</name>
<value>true</value>
</property>
<property>
<name>python</name>
<value>true</value>
</property>
<property>
<name>coldfusion</name>
<value>false</value>
</property>
<property>
<name>miva</name>
<value>false</value>
</property>
<property>
<name>write_modify</name>
<value>false</value>
</property>
<property>
<name>webstat</name>
<value>none</value>
</property>
<property>
<name>webstat_protected</name>
<value></value>
</property>
<property>
<name>www_root</name>
<value>C:\inetpub\vhosts\testdomain.com\httpdocs</value>
</property>
</data>
</result>
</get>
</subdomain>
</packet>

EXPECTED RESULT

<value>C:\inetpub\vhosts\testdomain.com\httpdocs</value> is NOT correct... I expected C:\inetpub\vhosts\testdomain.com\site1
 
Last edited by a moderator:
Is someone who use API working properly with subdomains?

I cannot manage them well nor in a linux system nor in this related windows 2008 server r2 x64. With windows, I pasted the related home directory error. In a linux system, API does not permit <home> tag and always create the subdomain on the "httpdocs" directory.

Two different OS, same problem (again). Subdomains are not Aliases :)
 
Last edited by a moderator:
Back
Top