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

Use Plesk API for post install server configuring.

P

Patrick M

Guest
Hi,

I work on an environment where we build Virtuozzo containers with Plesk server installed on each instance. All the steps are done through the Virtuozzo API and Plesk API. Building the container and intalling Plesk 9.3 works great. My final step is to reset the admin password on the Plesk control panel in order to prevent anyone from guessing the IP address of the installed Plesk, and inputting the default user/pass (admin/setup) that are selected on installation.

My approach is to use the Plesk API and call the SetPassword command as follows:
<packet version="1.5.2.0">
<server>
<set>
<password> + newPassword + </password>
</set>
</server>
</packet>

When sending this command, I get the following error:
Plesk is not configured. You should go to the control panel for postinstall server configuring.

I understand that on a typical manual installation, you have to login using the default user/pass and setup some configuration. The post install wizard asks a few questions like the contact infos and such. But I really don't want to do this manually before i can change the admin password. Remember that this whole process is automatic and waiting for someone to complete this step manually is far from ideal.

Is there a way to bypass this check and change the admin password through the plesk API?
Is there a way to complete the post install process through Plesk API calls?
 
I just saw a button in Virtuozzo Linux PIM that can be used to change the admin password manually.

Go to the container's Software tab, click Control Panels, and click 'Manage' under Plesk control panel.
The next windows show a 'Log In to Plesk' and a 'Change password' link.

What I want it this same functionality through either the virtuozzo api or the plesk api.

Anybody has seen a way to do this?
Someone at parallels must know how to do it, since you implemented it...
 
Back
Top