I suggest you ...

Firewall Management + fail2ban support

It would be useful to have the ability to configure the default firewall rules at server level, rather than relying on htaccess files which are useless for managing large data sets (i.e. IP lists/ranges).

Additionally, having fail2ban installed and bridging between the firewall would be extremely helpful for using plugins like wp-fail2ban, which automatically bans "bruteforce" login attempts at server level, rather than application level.

13 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

David Sherlock shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Greg commented  ·   ·  Flag as inappropriate

    On the Features page, CW advertises, "Proactive Cloudways security practices keep all your servers safe and secure. ... All Cloudways hosted servers are protected by OS-level firewalls that filter out malicious traffic and keep out the intruders." This is not completely true, and there's no way to know to what extent it may be partially true. I had to request help hunting down what was causing outages, come to find it was a single IP address from China repeatedly trying to log in to one site, and was told to ban it in htaccess. That is the opposite of "proactive" and "OS-level."

  • Greg commented  ·   ·  Flag as inappropriate

    Yeah there definitely needs to be a better way to handle blocking IP/requests at the server level. Trying to do this at the application level is just inefficient, time consuming and eats up more resources.

    The biggest issue with cloudways is the lack of automatic banning of brute force login attacks and vulnerability scan that are to aggressive. If there was a sever level solution to this Cloudways would be able to offer more secure and stable Cloud server solution then anyone else out there.

Feedback and Knowledge Base