• 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.
  • 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 Plesk monitoring does not work aafter 18.0.61 update

manos

Basic Pleskian
Username:

TITLE

Plesk monitoring does not work aafter 18.0.61 update

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.61, almalinux 8.9 latest, tested on 4 servers

PROBLEM DESCRIPTION

Plesk monitoring stopped after 18.0.61 update

Error message is (servername) took too long to respond.

STEPS TO REPRODUCE

Just update to 18.0.61 and press monitoring

ACTUAL RESULT

Servername took too long to respond

EXPECTED RESULT

To see the grafana graphs

ANY ADDITIONAL INFORMATION

Tested on 4 almainux servers with same result

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for your report. This is a known issue. A workaround is to login to Plesk using port 8443.
 
Back
Top