• 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 CloudFlare with modsecurity problem

infoo

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Plesk Obsidian v18.0.44_build1800220614.18
I installed the Plesk, after days not working, not reachable sites. In the logs I see the modsecurity blocked attackers (yet CloudFlare IP adresses) and nobody can visit the sites...
I don´t know why at 21th century is not integrated there CloudFlares real IP getting... I must completely disable the modsecurity to start working pages.
Is this normal? How get work with CloudFlare? Chinese free panel have this function too (aaPa...).
 
In apache nginx settings add this

#additional http and https directive
RemoteIPHeader CF-connecting-IP

#additional nginx directive
real_ip_header CF-Connecting-IP;

correct ip will be logged.

In fail2ban settings you have to add all CF ips as trusted or turn that off. Else if someone tries to bruteforce/attack your plesk panel,mail,ftp like yoursite.com:8443 CF ip will be jailed.
 
The whole point of banning attackers is to prevent them from connecting to your server at all. That doesn't work when all your traffic passes through cloudflare so the only addresses connecting to your server are all from cloudflare. For that to make sense, you would have to ban them at cloudflare, if that's possible with their api.
 
Back
Top