Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
quick-tutoriel opened this issue Jan 2, 2023 · 3 comments

Comments

@quick-tutoriel
Copy link

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
Copy link

mossroy commented Jan 3, 2024

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
Copy link

SkyHawkBre commented Jan 24, 2024

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
Copy link

I am being plauged by this issue. Any fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants