Error Message : context deadline exceeded (Client.Timeout exceeded while awaiting headers)

[quick-tutoriel]

Hello,

I have just installed the latest version of traefik-crowdsec-bouncer and since I have activated the bouncer, I have this in my logs frequently:

2023-01-02T18:19:14Z WRN An error occurred while checking IP "" | error=Get "http://crowdsec:8080/v1/decisions?type=ban&ip=172.20.0.1": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Can you explain me what it means and if there is an optimization method to avoid this alert message because on my supervision with UptimeKuma I see that the container is in alert?

Thank you in advance for your answers.

Guillaume

[mossroy]

I have the same bouncer logs.
Theses logs give latencies of several seconds. It seems that when it reaches 5 seconds, this error message appears. And the corresponding HTTP request does not succeed.
I've tried to move the lapi pod to a faster node, but it was not better. I also tried to put traefik, its bouncer and lapi on the same node: not better
It seems to me that #21 would be needed in my case.

[SkyHawkBre]

I just got Crowdsec up and running yesterday in my homelab but today when trying to access some of my services they were coming up as forbidden with the same error:
WRN An error occurred while checking IP "" error="Get \"http://crowdsec:8080/v1/decisions?type=ban&ip=X.X.X.X\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Anyone have any suggestions or found a solution?
Thanks!

[loukaniko85]

I am being plauged by this issue. Any fix?

[schumi2004]

I'm on the same boat.
It's annoying because sometimes services don't respond until checks succeed

[mossroy]

This repo has not been updated since 3 years.

I switched to https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin with no regret. It implements caching, and even a "stream" mode where all the information is kept in memory by the plugin, to avoid network fetches