• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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