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

Issue Monitoring of Plesk web server service does not work (since Plesk 8)

K

King555

Silver Pleskian
I upgraded to Plesk 12.5 one day ago. I was suprised that there is still a bug, which I have since Plesk 8 and which I reported for every version now.

The monitoring of the Plesk web server service does not work. I can activate it, but it's deactivated some minutes later, because the server is not reachable. But Plesk works fine!

I have a possible reason for that: My Plesk only listens on a specific IP and port. Maybe Watchdog tries to connect to port 8443? It will not find Plesk there.

Edit: Maybe I should have posted this into the Feedback forum?
 
Last edited:
You must log in or register to reply here.

Similar threads

K
Resolved Watchdog says Plesk Web Server down since 18.0.79
Replies
3
Views
1K
King555
K
Azurel
Question Could someone share their "ss -tulpn" output from AlmaLinux 9?
Replies
6
Views
1K
Azurel
Azurel
S
Resolved Monitoring shows errors 'Dashboard not found' or 'An unexpected error occurred'
Replies
2
Views
3K
Sascha Schlüter
S
Azurel
Input AlmaLinux8to9 upgrade leaves Plesk in broken state with insufficient service checks and recovery guidance
Replies
2
Views
2K
Azurel
Azurel
Z
Resolved Bug report: Watchdog disk threshold alert email contains literal placeholders instead of values
Replies
7
Views
9K
Zenon
Z
Back
Top