• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Upgraded to 8.3 and Website Crashed

H

hometownf

Guest
We upgraded our Plesk to 8.3 and all of a sudden the site went missing. We were told from godaddy:

"The error appears to be caused by the username htfashions being in the Plesk MySQL database already. This is causing the backup error that you are encountering. We recommend removing the hometownfashions.com domain account from Plesk completely, setting it up again, then attempting the backup. If you continue to have issues, we will be happy to investigate the further. Please also provide the specific steps you are taking before encountering the error."

We did everything godaddy told us, and we cannot get the backup to restore.

PLEASE HELP!!!!!!!!!! Our site is down and we are losing $$ by the minute.
 
Back
Top