• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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