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

Question DDoS Attack on Plesk Server +

issjenuw

New Pleskian
Server operating system version
almalinux
Plesk version and microupdate number
18
I have been facing a huge DDoS attack against my Plesk server, which hosts around 250 accounts. The attacks were causing very high load and making several websites slow or completely inaccessible

I recently installed BashEdge plugin for plesk on the server, and so far it has been working great. It is blocking a large amount of the attack traffic and the server has remained stable. I have attached a screenshot of the attack statistics.

I do have one question. Most of my domains are already behind Cloudflare. If I enable BashEdge Lockdown Mode during a heavy attack, could it cause any issues with Cloudflare traffic or accidentally block/challenge Cloudflare IPs?

Has anyone used Cloudflare together with BashEdge Lockdown Mode?
 
@King555 That's correct. I misread that. Nevertheless, I would still check whether my assumption is correct and which domain the attack is targeting, so that we can recommend further measures.
 
Exactly. The attack stopped completely after enabling the plugin. the question is they have an Lockdown mode and i am using it with cloudflare under attack mode. will it cause any conflict ?
 
Exactly. The attack stopped completely after enabling the plugin. the question is they have an Lockdown mode and i am using it with cloudflare under attack mode. will it cause any conflict ?
Yes, Cloudflare Under Attack Mode can be quite aggressive and may challenge legitimate traffic as well, including search engine bots such as Googlebot.

If the attack has already stopped after enabling the plugin, I would consider disabling Cloudflare Under Attack Mode and using a more targeted custom Security rule instead.

For example:

Code:
(ip.geoip.country ne "AU") and
not cf.client.bot

This is only an example and should be adjusted depending on where your legitimate visitors are coming from.

I would also check the bot activity in Cloudflare. It may be worth looking specifically at AI crawlers, as some of the traffic could be coming from bots scraping content from the website. Some AI bots, such as meta-externalagent, can be particularly aggressive.

I haven’t used BashEdge myself, so I can’t really comment on that part.
 
Back
Top