• 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.

Issue Create site with secret_key without Public IP generate error 11003

MicheleP

Basic Pleskian
New Plesk setup, Obsidian 18.0.38
Forgot to setup Public IP in Ip Adress
Create secret_key form CLI, create new site with XML API using this key
Got error Plesk error [11003]. Id site 0, .... but in Plesk the site is there .... whats wrong now ...
To make short ... setup the Public IP, recreate a new secret key, used this new one with API all works fine...
Plesk say the public IP is optional, it seems really not true
 
Back
Top