• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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