• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Question Rest API subdomain does not use custom Doc Root

Kees

New Pleskian
Hi,

I'm using the REST api for creating subdomains. I have the custom document root set up to /public in panel.ini which works if i add a new domain or subdomain manually.

Whenever i create a subdomain over the API it does not set the document root to /public but just to /site1 /site2/ (btw it also does not allow for setting folder name but we've solved that by saving it). You would think the API perform the exact same action as manually adding a subdomain...

Any ideas how to solve this?
 
Last edited:
Back
Top