• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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
793
TimReeves
TimReeves
T
Issue Unbanning some IP addresses causes the server to be unresponsive
Replies
4
Views
879
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
4K
cmaxwell
C
M
Issue Upgrade Debian 11.9 to 12 fails
Replies
0
Views
646
MartinT
M
Back
Top