1. Caddy version (caddy version
):
2. How I run Caddy:
Docker via slothcroissant/caddy-cloudflaredns
a. System environment:
See: Aborting with incomplete response
b. Command:
See: Aborting with incomplete response
c. Service/unit/compose file:
See: Aborting with incomplete response
d. My complete Caddyfile or JSON config:
See: Aborting with incomplete response
3. The problem I’m having:
I’d like to see if there are ways one could debug the error "http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"
.
I know it’s not an “issue” per se - however my docker logs are absolutely piled full of this error message and if nothing else, I’d like to figure out what application I’m hosting behind Caddy is causing it so I can dig in further if needed. (Alternatively, a way to silence this log would be nice ).
I’ve tried some debug log things, but I couldn’t seem to get anything beyond what’s shown below to populate:
{"level":"error","ts":1646670691.8830473,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670692.884886,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670697.0600572,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670731.007158,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670736.8877547,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670738.0831406,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670765.9784184,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670771.9227834,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670773.1522548,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670798.1662176,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670800.997856,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670806.9451797,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670835.9819987,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670842.0014179,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670843.190441,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670870.9814303,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670876.9677038,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670878.1804051,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
{"level":"error","ts":1646670902.0273228,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","error":"context canceled"}
My current debug logs ref:
log {
level DEBUG
output file /data/logs/caddy.log {
roll_size 10MiB
roll_keep 10
roll_keep_for 336h
}
format json {
time_format iso8601
}
}