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

Issue Bug in Plesk 12: Watchdog monitoring of "Plesk Web Server" fails

King555

Regular Pleskian
(I already posted this bug in another thread, but that thread is in a sub-forum for older versions of Plesk)

The Watchdog monitoring of "Plesk Web Server" does not work (it says, it is not running). But the Plesk Web Server is online, I can access Plesk at any time without problems. This problem occured in Plesk 8.x, 9.x, 10.x, 11.x and now in 12.x.

Plesk 12 (latest update)
Debian 7.6 x64
 
Because I had this bug in all Plesk versions and until now nobody else seems to have this problem, I had an idea:
Does Watchdog checks the Plesk web service via connecting to it's port? If yes: I only allow connections on a specific (not default) port and on a specific IP. If Watchdog tries to connect to localhost:8443 or the server's main IP on 8443, it will fail.
 
That reminds me of issues i had in the past with Watchdog on CentOS resulted in corrupt nginx, apache config files or wordpress directories.
After restoring a full backup image. I deactivated a couple of Watchdog services and all is now running good.
 
Back
Top