• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue 18.0.47 update #5 caused server to become unreachable

dakkafex

New Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
18.0.47 Update #5
18.0.47 update #5 caused multiple of our servers to become unreachable.
It could also not be pinged and it was unreachable by ssh, the only thing that fixed was manually restarting the VPS instances.

I have tried digging through the logs, but I didn't see anything that looked like something that would prevent the server from starting.

Does anyone know what could have caused this? or what should I be looking for in the logs specifically.
 
Looks like a Fail2Ban ban. Do you see the server's own IP address or 127.0.0.1 in /var/log/fail2ban.log?
 
You you see your own ADSL public IP in that log?
The point is that ping and SSH are two different things. If SSH crashes, the network interface itself and the kernel will still live.
What shows up in /var/log/messages at the time when the crash occured?
 
Back
Top