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

Looking for Plesk expert that can fixed b0rked 7.5.4 -> 8.2 server

M

mousehouse

Guest
Hello forum,

We hired a smart Plesk-partner to upgrade our FreeBSD 6.2 + Plesk 7.5.4 setup to Plesk 8.2. The upgrade has failed almost completely and the Plesk-partner is for some reason not responding.

Now before we go setup a new server and attempt to psadump and -restore our clients, is there someone willing to fix our server?

Problems are:
- Certain actions result in a Plesk DB Exception (such as clicking the Mail button for a domain).
- Webmail is borked (not present in the Includes).
- Protected directories are broken.
- Domain Administartors are broken. DB exception.
- Uploads are broken because upload temp path is missing / changed / permissions ?

If someone is willing to take the job, send me a message with the tarif you're asking and a reference please.

regards
 
We are able to solve most issues with our Plesk partner.
 
Back
Top