• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Input Enhancing error reporting for "Plesk Exception Database" issues

Maarten

Golden Pleskian
Plesk Guru
I've noticed a growing number of posts about the "Plesk Exception Database" errors recently. It would help most users if the error screen showed more detailed information about what's happening on the server, like free memory, free disk space, CPU load, and any relevant details related to this problem.

For advanced Plesk users, the error screen below is fine, but for users not used to working with the command line, this can be quite challenging. Especially when the "Open Repair Kit" button doesn't work, which also happens occasionally.


Screenshot 2023-10-30 at 17.06.36.png
 
Back
Top