# HAProxy WordPress abuse protection

**URL:** <https://discourse.haproxy.org/t/haproxy-wordpress-abuse-protection/499>\
**Category:** Help!\
**Created:** [July 14, 2016, 8:28pm UTC](https://discourse.haproxy.org/t/haproxy-wordpress-abuse-protection/499 "2016-07-14T20:28:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![c0r3dump3d](https://avatars.discourse-cdn.com/v4/letter/c/a587f6/32.png) [@c0r3dump3d](https://discourse.haproxy.org/u/c0r3dump3d)\
**Post date:** [July 9, 2018, 1:06pm UTC](https://discourse.haproxy.org/t/haproxy-wordpress-abuse-protection/499/2 "2018-07-09T13:06:26Z")

</div>

Hi, I have the same problem, I have posted this new topic …

> [@Bruteforce Wordpress](https://discourse.haproxy.org/t/bruteforce-wordpress/2706):
>
> Hi, I’m trying to implement a Wordpress bruteforce protection at haproxy level, version 1.5.18 in CentOS 7. I’m folowing the manual [https://www.haproxy.com/blog/wordpress-cms-brute-force-protection-with-haproxy/](https://www.haproxy.com/blog/wordpress-cms-brute-force-protection-with-haproxy/) but I’m not able to make it work. In the frontend section I have: tcp-request inspect-delay 10s tcp-request content accept if HTTP acl wp\_login path\_beg -i /wp-login.php acl flagged\_as\_abuser sc1\_get\_gpc0 gt 0 stick-table type binary len 20 size 500 store gp…

---

_[View the full topic](https://discourse.haproxy.org/t/haproxy-wordpress-abuse-protection/499)._
