-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Long processing times while uploading to S3 #19223
Comments
By the way, to complete this issue, sometimes some chunks are "missing" on S3 storage (404 Not found) ! So the assembling step is failing. Maybe there should be some checks when sending chunks to S3, if they are not correctly saved, maybe resend them... |
I can confirm this happens for me too (error 524) without cloudflare – only when uploading files larger than 1GB. Note that the uploading process finishes fine, the error raises on processing (presumably chunks) on the s3 storage. `Error: fclose(): supplied resource is not a valid stream resource at /var/www/nextcloud/3rdparty/icewind/streams/src/Wrapper.php#96
I'm using latest nextcloud version to date. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
My Nextcloud snyc windows client also have this issue, in my windows nextcloud logs says 524, which is cloudflare issue, check the server load and response both are ok, what I know is the Sync client sync a large file, it stop for a while at the sync process. so I blame nextcloud sync client, lol. why it stop, keep going |
Running Nextcloud 17.0.3 behind Cloudflare works fine, unless the upload processing time takes longer than 100s (in our case, uploading files bigger than 2GB trough WebUI to a S3 primary backend). In that case, Cloudflare returns a
524
.Error when assembling chunks, status code 524
Contacting Cloudflare about this hits on a:
Cloudflare will typically wait for a HTTP response from origin server for 100 seconds. If no response (or
<8Kb
) is sent by the origin in that time, Cloudflare will close the connection and serve a 524 error page.So the question is, can (should?) Nextcloud detect those long running processing times and send a
keepalive
request every (say) 60 seconds to avoid these problems on some proxies like Cloudflare?The text was updated successfully, but these errors were encountered: