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

Paid for Plesk support and don't get any reply

C

chris@virtbiz

Guest
In Previous Plesk versions email users could manage their own settings such as autoresponders. Now with Plesk 10 they are unable to do so. Our customers are upset about this.

I paid for a Plesk support incident well over 12 HOURS ago and received my order confirmation from Digital River. I have an Order ID, but the Plesk ticket will not create because I haven't received a valid Support Code. I have entered the Plesk Key that I used on the order, but it doesn't work.

I tried calling Parallels but the automated call tree always winds up hanging up on me after 10 minutes on hold.

At this point I am so frustrated I will be moving all customers away from Plesk and charging back recent SUS fees and of course the support fee. This is horrible implementation of features and even worse treatment of a customer. I don't expect Parallels to pay attention, but want to make sure that it's made public so that others don't also fall into this trap.
 
Back
Top