• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

rebuild plesk configuration

C

cosmicfantasia

Guest
Hi,

My hard drive on a machine failed. My host reinstalled Plesk on a new drive, and put the old hard drive in the machine as well. I have mounted the old drive and can access it to copy all files over.

My question is, where are all file/directories that I need to copy over to make Plesk on my new hard drive come up with all the data and configuarations of the old hard drive?

Currently, I have recurisvely copied over /etc/psa and /etc/psa-horde

Now when trying to access Plesk I get:

ERROR: Unable to connect to database: saved admin password is incorrect. 0: /usr/local/psa/admin/auto_prepend/auth.php3:81 psaerror(string "Unable to connect to database: saved admin password is incorrect.")

Will this be fixed when all configuration files have been copied over? If not, how do I fix this?

Thanks,
Eric...
 
more info...

Have now found /var/lib/mysql/psa and /usr/local/psa and copied over.

Still mysql error whne trying to access PSA. Are there more config files to copy over?

Eric...
 
Was able to fix password problem with help from:

http://kb.swsoft.com/article_16_346_en.html

:)

But haven't got all the data (user accounts) over yet after copying over:

/etc/psa
/etc/psa-horde
/var/lib/mysql/psa
/usr/local/psa

What else needs to be copied?

Also, when restarting PSA with /etc/init.d/psa restart I get the following:

/usr/local/psa/admin/bin/httpsdctl restart: httpd restarted
packagemng: Unable to create 'dirty' flag in the PRODUCT_ROOT_D/var: Permission denied
System error 13: Permission denied
packagemng: Unable to create 'dirty' flag in the PRODUCT_ROOT_D/var: Permission denied
System error 13: Permission denied

Is this related or a major issue?

Eric... :)
 
Back
Top