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