Mohammed90
February 13, 2025, 12:01am
13
Honestly, I’ve been looking at this topic on and off, and I’m not sure what’s happening. Request cancellation in-and-of itself isn’t an error, but it appears to be cancelled inadvertently or unintentionally. I don’t use Jellyfin so I’m not familiar with the options available on the client, but is there something about network bandwidth or performance to tweak?
I’ve two other reports of the same error, but I don’t know if they’re the same issue:
Error logs:
ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 logger=http.handlers.reverse_proxy ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 logger=http.handlers.reverse_proxy msg=aborting with incomplete response ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 ERR ERR ERR ERR ERR ERR ERR ERR ts=1717566007.683709 logger=http.handlers.reverse_proxy ERR ERR ERR ERR ERR ERR ER…
opened 01:47PM - 19 Aug 23 UTC
upstream
I often receive the following error in my caddy logs while doing speed tests wit… h [librespeed](https://github.com/librespeed/speedtest):
```json
{
"level":"error",
"ts":1692452491.2814867,
"logger":"http.handlers.reverse_proxy",
"msg":"aborting with incomplete response",
"upstream":"localhost:8085",
"duration":0.005322624,
"request":{
"remote_ip":"192.168.178.20",
"remote_port":"60436",
"client_ip":"192.168.178.20",
"proto":"HTTP/3.0",
"method":"GET",
"host":"speed.example.com",
"uri":"/backend/garbage.php?r=0.6473048564721796&ckSize=100",
"headers":{
"Accept-Encoding":[
"gzip, deflate, br"
],
"Sec-Fetch-Mode":[
"cors"
],
"User-Agent":[
"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0"
],
"X-Forwarded-For":[
"192.168.178.20"
],
"Referer":[
"https://speed.example.como/speedtest_worker.js?r=0.8378941592896734"
],
"Sec-Fetch-Dest":[
"empty"
],
"Sec-Fetch-Site":[
"same-origin"
],
"Cache-Control":[
"no-cache"
],
"Alt-Used":[
"speed.example.com"
],
"Accept-Language":[
"de,en-US;q=0.7,en;q=0.3"
],
"Dnt":[
"1"
],
"Pragma":[
"no-cache"
],
"Accept":[
"*/*"
],
"X-Forwarded-Proto":[
"https"
],
"X-Forwarded-Host":[
"speed.example.com"
]
},
"tls":{
"resumed":true,
"version":772,
"cipher_suite":4865,
"proto":"h3",
"server_name":"speed.example.com"
}
},
"error":"writing: stream 80 canceled by remote with error code 268"
}
```
The mixture of HTTP/3 and librespeed canceling the requests seems to trigger this (bogus?) error.
If you’re good with networks, try using Wireshark to trace what exactly happens. It’ll be hard for me to investigate it myself because the reports are not reproducible.
1 Like