• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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