# Counter issues on 1.8.29

**URL:** <https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381>\
**Category:** Help!\
**Created:** [March 23, 2021, 9:01pm UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381 "2021-03-23T21:01:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Victor](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/victor/32/393_2.png) [@Victor](https://discourse.haproxy.org/u/Victor)\
**Post date:** [March 23, 2021, 9:01pm UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/1 "2021-03-23T21:01:53Z")

</div>

Hi,

We’re using some restrictions like this:

```
stick-table type ip size 1m expire 30s store gpc0,conn_cur,conn_rate(3s),http_req_rate(10s),http_err_rate(30s) peers mypeers

# Reject over 50 concurrent connections per ip
tcp-request connection reject if { src_conn_cur ge 50 }
# Reject if more than 30 connections in 3 seconds
tcp-request connection reject if { src_conn_rate ge 30 }
# Reject more than 30 http requests in 10 seconds
tcp-request content reject if { src_http_req_rate ge 30 }
# Reject if more than 10 http errors in 30 seconds
tcp-request content reject if { src_http_err_rate ge 10 }

```

While they’re not terribly nice, they used to work as expected. After upgrading to 1.8.29 we do get connection reset at normal browsing, a few requests from a browser, definitely none of the above limits being hit. There are two proxies in peering.

Downgraded back to 1.8.28 restored the expected behaviour. There was no configuration change.

Thanks,  
Victor

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [March 23, 2021, 10:37pm UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/2 "2021-03-23T22:37:29Z")

</div>

Yes, this is a known a new regression in the latest bugfix releases, patches have been posted and committed to 2.2 tree, other backports will follow:

[https://www.mail-archive.com/haproxy@formilux.org/msg40020.html](https://www.mail-archive.com/haproxy@formilux.org/msg40020.html)

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [March 24, 2021, 10:01pm UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/3 "2021-03-24T22:01:45Z")

</div>

All supported stable branches now have the fix.

You can git clone from the 1.8 branch, or get get the backported patches here manually:  
[http://git.haproxy.org/?p=haproxy-1.8.git;a=patch;h=bfba403a925c954daf6f43a3239429044681316b](http://git.haproxy.org/?p=haproxy-1.8.git;a=patch;h=bfba403a925c954daf6f43a3239429044681316b)  
[http://git.haproxy.org/?p=haproxy-1.8.git;a=patch;h=491b86ed0acdb4f3a1673f9357240176da930548](http://git.haproxy.org/?p=haproxy-1.8.git;a=patch;h=491b86ed0acdb4f3a1673f9357240176da930548)

(both are necessary). Tomorrows 1.8 snapshot [haproxy-ss-20210325.tar.gz](http://www.haproxy.org/download/1.8/src/snapshot/haproxy-ss-20210325.tar.gz) will also contain those fixes.

I’ve also filed a tracking issue at github:

> <https://github.com/haproxy/haproxy/issues/1196>
>
> This is a tracking issue only for a bug that is already fixed in all supported, affected trees.
> Detailed description of the...

---

<div class="post-metadata">

**Author:** ![Victor](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/victor/32/393_2.png) [@Victor](https://discourse.haproxy.org/u/Victor)\
**Post date:** [March 25, 2021, 12:48pm UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/4 "2021-03-25T12:48:18Z")

</div>

Thanks Lukas, 1.8.29 plus the two patches is working fine.

---

<div class="post-metadata">

**Author:** ![joel-l](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/joel-l/32/550_2.png) [@joel-l](https://discourse.haproxy.org/u/joel-l)\
**Post date:** [March 26, 2021, 10:50am UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/5 "2021-03-26T10:50:25Z")

</div>

Do you happen to have an estimate as to when the fixes might be available as a new release for the 2.2 version (as 2.2.12)?

Asking because I’m using prebuilt packages and can’t easily patch anything manually.

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [March 26, 2021, 11:50am UTC](https://discourse.haproxy.org/t/counter-issues-on-1-8-29/6381/6 "2021-03-26T11:50:10Z")

</div>

[https://www.mail-archive.com/haproxy@formilux.org/msg40050.html](https://www.mail-archive.com/haproxy@formilux.org/msg40050.html)

> 2.2.12: probably early next week to still give some time for last issues  
> to be reported.

An alternative is 2.3.8, although that is not a LTS branch.