• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Issue fatal: Timeout before authentication for [IP-ADDRESS] port 44745

Is there any way to stop this reporting in console, as I can confirm it happens only on freshly installed Debian 12.

It doesn't occur on systems updated to Debian 12.
I can also confirm this. Last week I upgraded a Debian11 with Plesk to Debian 12 (following the manual steps detailed here: https://support.plesk.com/hc/en-us/...-upgrade-procedure-on-Linux-server-with-Plesk), and these messages are not showing in this server.

They are still happening in all Debian 12 servers with fresh installs.
 
The reason behind is a different system logging daemon.

The upgraded Debian 12 systems are normally using rsyslog as default system and kernel logging daemon. Installing Plesk on a fresh Debian 12 installation leads to the usage of syslog-ng as default system logging daemon.

Is there any recommendation by Plesk, which one should be used for best compatibility? Should upgraded systems be switched to syslog-ng too?
 
Back
Top