etsythemeshop

@mtgarmorydotcom — yes, but it’s very difficult. There are no actions/hooks provided by woo-commerce. You need to find a way to cleanly hook into wp_clean yourself and stop it from doing it’s thing to *just* the attributes. Good luck!

Thank you!

for #1) There is a DDOS XMLRPC attack that is carried out by hitting xmlrpc.php many times in succession without triggering the authentication failure — it’s very common so I do believe it should be rate-limited.

Adding this to jail.local fixed my problem in ubuntu 14.04 LTS:

[DEFAULT]
backend = polling

I had to put this line to each [wordpress-*] subsection:
port = http,https

@foliovision

would you mind posting your fixes independently?

tmacka88, did you find it out? I have the same problem.

fail2ban-regex /var/log/auth.log /etc/fail2ban/filter.d/wordpress.conf

Running tests
=============

Use   failregex file : /etc/fail2ban/filter.d/wordpress.conf
Use         log file : /var/log/auth.log

Results
=======

Failregex: 74 total
|-  #) [# of hits] regular expression
|   7) [74] ^\s*(<[^.]+\.[^.]+>)?\s*(?:\S+ )?(?:kernel: \[\d+\.\d+\] )?(?:@vserver_\S+ )?(?:(?:\[\d+\])?:\s+[\[\(]?wordpress(?:\(\S+\))?[\]\)]?:?|[\[\(]?wordpress(?:\(\S+\))?[\]\)]?:?(?:\[\d+\])?:?)?\s(?:\[ID \d+ \S+\])?\s*Pingback error \d+ generated from <HOST>$

–

fail2ban-client status wordpress
Status for the jail: wordpress
|- filter
|  |- File list:	/var/log/auth.log
|  |- Currently failed:	0
|

– Total failed: 0

- action
   |- Currently banned:	0
   |

– IP list:
`- Total banned: 0
`