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

Resolved MySQL Process List (Beta), request failed with status code 500

MicheleB

Regular Pleskian
I'm using the 18.0.21 #5 version (no possibile to update to the last 18.0.23) and when I try to see "MySQL Process List" I receive this error:
request failed with status code 500

2020-01-27_09-37-40.png

This is the configuration of the cloud server:
OS:
CloudLinux release 7.7 (Valery Bykovsky) x86_64

Product:
18.0.21 CentOS 7

Upgrade history:
2019-12-22 18:21:10 18.0.21 NULL CentOS 7.7.1908 5
2019-12-22 19:18:12 18.0.21 NULL CloudLinux 7.7 5

Nginx enabled:
yes

Database server:
MySQL 5.7.29
 
I've found this bug reported with id "PPPM-11086" but I don't know if is safe to apply the "resolution"; I need to ask to my hosting provider because I don't know which is exactly the "admin password" of my cloud server (they gave me a username "root" to Plesk access):
 
A little "unresolve" status magic would be nice on this post -

Has anyone running 18.0.28 reported this as a bug?
 
Back
Top