• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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

K

King555

Regular 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 Monitoring Plesk port via uptimerobot.com makes trouble since (ca.) version 18.0.65
Replies
13
Views
2K
King555
K
K
Issue A lot of random "500 Internal Server Error" from nginx since March 10th
Replies
13
Views
2K
alvarezcruz
alvarezcruz
K
Issue Monitoring extension uses another language than the rest of Plesk
Replies
9
Views
1K
King555
K
C
Question Monitoring a Plesk Server (services, domains, etc.) with Zabbix
Replies
2
Views
1K
Faris Raouf
F
L
Input The future of Plesk? pros, cons... not a bash the company thread
Replies
0
Views
895
larryk
L
Back
Top