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

Logwatch relevance to Plesk

iantresman

Basic Pleskian
I believe that the Logwatch file I receive via email each day, is sent by the operating system, and not Plesk.

It would be useful to have a summary explanation of some of the Logwatch entries, and how they relate to Plesk, for example, are there Plesk settings that need to be made to "fix" certain issues". Some of the entries that look concerning include:

* A total of 6 sites probed the server
* Named Begin: **Unmatched Entries**
* sshd: Authentication Failures
* proftpd-messages Begin: **Unmatched Entries**
* Failed logins from
* Illegal users from

Note (added later): It seems that Logwatch is a set of independent scripts that comes installed with some Linux operating systems. The Logwatch home page is here, though there is not too much information there.
 
Last edited:
Back
Top