stashapp / stash

An organizer for your porn, written in Go. Documentation: https://docs.stashapp.cc
https://stashapp.cc/
GNU Affero General Public License v3.0
9.38k stars 803 forks source link

[Bug Report] Slow loading and unknown responses #5003

Open urandom730 opened 5 months ago

urandom730 commented 5 months ago

After skipping ahead (or back) in a video the loading becomes really slow after a while, which causes the website not to load (solid few minute or so). Followed by this log:

WRN Response: 0 Unknown httpRequest={"proto":"HTTP/1.1","remoteIP":"...","requestID":"0498a390aa63/gK73rOrpGF-000008","requestMethod":"GET","requestPath":"/graphql","requestURL":"http://.../graphql"} httpResponse={"bytes":0,"elapsed":89597.912081,"status":0} service=stash

After the response has been retrieved, it works like normal again until skipping ahead a few times again.

Stash Version: latest (docker)

Platform: Mobile, browser, same behavior from everything.

Shiroihige commented 4 months ago

I also am experiencing a similar issue.

feederbox826 commented 3 months ago

One of the factors that I've helped users discover is Cloudflare Tunnels, which throttle non-html traffic similarly to this, or their servers just being overwhelmed by transcoding

mjd515 commented 1 week ago

i am having the same issue. i am not using CF tunnels nor am i transcoding. in fact when transcoding this issue is less pronounced. my site does use cloudflare but i have it set to bypass caching using page rules. i think it has something to do with interactive heatmaps and traefik. in my traefik logs i see a 404 when interactive heatmaps are requested. all other requests in my traefik logs are 206 which i suspect are normal due to the video playback nature.

feederbox826 commented 1 week ago

404 when interactive heatmaps are requested

This is normal behaviour if you don't have funscripts and interactive heatmaps generated

CF cache is not where the throttle happens, you need to have it not proxied (grey cloud)

mjd515 commented 1 week ago

ah ok so its a cloudflare proxy issue not tunnel, although i am sure that is an issue since you need to use the proxy to use the tunnel. can confirm that indeed when not proxied and just using DNS it loads as usual. i wonder what specifically changed in the last few months that made this issue.

feederbox826 commented 1 week ago

https://blog.cloudflare.com/updated-tos/#snip-snip Instead of outright banning it, like historically suspending user's accounts, they've instead throttled performance to push users towards their own services for it