• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 fatal: Timeout before authentication for [IP-ADDRESS] port 44745

Daveo said:
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.
Click to expand...
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?
 
You must log in or register to reply here.

Similar threads

TimReeves
Issue Messages from a Plesk component appearing on root ssh console
Replies
9
Views
995
TimReeves
TimReeves
T
Issue Unbanning some IP addresses causes the server to be unresponsive
Replies
4
Views
992
TurabG
T
wakabayashi
Resolved Fail2Ban - Postfix not working for SASL (bug?)
Replies
4
Views
1K
mizar
mizar
J
Issue apache2 proxy target - wrong ip-address
Replies
5
Views
5K
cmaxwell
C
M
Issue Upgrade Debian 11.9 to 12 fails
Replies
0
Views
707
MartinT
M
Back
Top