• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Create a Site using XML API return 1006 Permission denied

puppy

New Pleskian
I'm trying to use the XML API provided by Plesk,
except adding related APIs,
whether I use account verification or Secret Key verification,
it always successfully execute the APIs (I tested modifying subdomain api and deleting subdomain api),
however, the API for adding related functions(I tested creating site api and creating site api) will return "1006 Permission denied".
I would like to see if there is any way to solve this problem

By the way,
I am making API calls as a Plesk Customer account,
Not an Administrator account,
Is this just a permissions problem?
I refer to the link below,
and it shows that it has the permission to support the customer account.

If there is a solution,
thank you for providing!
 
I'd like to chip in that an upgrade to the latest Plesk version could be a good idea as from version to version many known issues are being fixed. Maybe an upgrade will already solve the issue?
 
Like @Peter Debik suggested it's best to update Plesk to the latest version and test again. If you still encounter an error after updating to the latest Plesk version please post your API payload body here.
 
Back
Top