-
Notifications
You must be signed in to change notification settings - Fork 334
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
Caddy v2 - issues with dozzle, continuous spamming log reading: context canceled
#2844
Comments
Interesting. I haven't been able to reproduce this. I used Caddy for a while before moving to Traefik. I don't think Would you be able to provide a minimum example for me to test it? Also have you tried disabling proxy buffering as suggested caddyserver/caddy#677 (comment)? |
Hmm seems like this is expected with SSE. So maybe there isn't anything to fix. |
So you have used caddy before and had no error like this.. I don't know I've always have it. So to understand, that error is being printed only when I'm inside dozzle. Clicking on any container (I have about 50) will print one error. Clicking 5 times = 5 errors. Clicking back and forth between containers will print erorrs all the time. I got used to ignore the caddy container alltogether cause all I see is this error. But decided to post here, just in case there'll be a fix :) As for those headers... Thanks for your reply. In the end it's no big deal, maybe this should have been addressed by caddy long ago, but they choose to ignore it. If I know how to filter it, I would. |
Nice I was able to reproduce it finally. I agree it is annoying. If there is a fix I can do on my side then I'll fix it. Let me take a look. |
Alright, I did a lot research. Unfortunately this is an error that is being thrown at language level inside Caddy. https://caddy.community/t/filter-out-noisy-logs-aborting-with-incomplete-response/12834/3 suggests to just grep them out. There isn't anything I can do on my side to avoid these logs. It will have to be done from Caddy. I wish at the very least the errors could be moved to debug. |
Amir, thanks for looking into it. I didn't have my hopes high either, knowing this was around for such long time. Have a peaceful sunday and thanks for your lovely dozzle! It rocks (btw I read the docs after a long time and added forward auth envs and discovered I can restart/stop containers as well) 🥇 So nicee!
|
By the way, the reason why you see this error with Dozzle is that Dozzle uses server side events. Caddy throws this error every time a web socket or SSE is reset. Other apps don't use this type of connection as often. |
There is no fix, it should come from caddy, they ve been aware of it for quite a while, but it's not an issue in their view. |
Is there still no way to hide this error in Caddy ? |
apparently not. If you find one, do post :) |
Is your feature request related to a problem? Please describe.
I'm using caddy and also using dozzle on my machines, which I love deeply.
However, they have a love-hate relationship, since using dozzle, my caddy log continuously spams some error I will show below. Do note this error is not new, I've had it for years.
I manage to fix all other containers, but I cannot with dozzle.
Other containers which had output this error were fixed by removing these headers which I previously had included.
But with dozzle, I don't have them, still the error is present.
Can you suggest a solution?
I think it's related to the headers (gzip) or something.
I've searched about this error in google, every time it pops up, dozzle is involved, mostly is a harmless error, but I narrowed it down to dozzle being the only container which still triggers it. (other offenders were fixed by removing my added headers in caddy. However, dozzle naked, without any header added, still won't stop the spam.
This is the log error, appearing everytime I click on a dozzle log container.
My guess is
add Accept-Encoding=[ "gzip, deflate, br, zstd" ]
but I could be wrong.Describe the solution you'd like
To not have the error every time.
Additional context
This is my setup with dozzle:
Caddy
Docker
The text was updated successfully, but these errors were encountered: