-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[NC 20] "cURL error 28: Operation timed out" when uploading big files to nonlocal federation share #26071
Comments
Hi there, are you able to upload such big files via a normal public link to that specific server? |
Yes, this works without any error (tested with 599MB). The error on the federated share still exists. |
Same problem here, tested with Apache and Nginx, php7.4-fpm and php8.0-fpm, all combinations, Nextcloud 22. That's not the expected behavior, the file should upload directly to the federated server. P.S. This problem is also if we try to download a big file from federated folder. It's trying to download from my server, but in the same time is downloading in background from federated folder, which takes time. After finish downloading from federated folder(in background) it will give me the message to download the file (if not timing out waiting to pull the file) |
The same timeout hits in other situations. I have a file that I want to move into a federated share using the web UI, and the move fails reproducibly with the same error – shown as a generic “Could not move ” in the UI, but logged with details:
|
I have the same problem with NC 21.0.4, but I found a workaround here: https://help.nextcloud.com/t/curl-error-28-operation-timed-out-after-xxxxxx-milliseconds-with-xxxxxx-out-of-xxxxxx-bytes-received-see-http-curl-haxx-se-libcurl-c-libcurl-errors-html/67621 I set the timeout to 3600 in /path/to/nextcloud/lib/private/Http/Client/Client.php and the upload to my federated share works without any issues. I tested it with 1.5GB big files. The setting will be overwritten if you update Nextcloud to a new version |
Update: This issue is not resolved in NC v23 (at least for my instance). @getle87 The fix you linked seems to resolve the issue for some of my files but not for all. The error message changes to *Server replied |
@maxkratz |
@maxkratz , that fix is not a fix, it's just a little hack. When you upload a file to federated share, that file is uploading first on your server. After finishing, that file is uploading in the background to where is actually supposed to upload, on the federated share. |
@kingul Thank you for the explanation. I've increased the timeout to 7200s ( |
If I understand things correctly #33087 might fix this issue. |
This comment was marked as resolved.
This comment was marked as resolved.
Sadly, it did not fix it for us. I'm on version 25.0.3 (hosting the shared folder) and my friend is on version 25.0.1. He cannot upload large files into my folder, with the same error as described in this issue. Or is this issue only fixed in 25.0.3? |
He just updated to 25.0.3, too, so we're both running the same version. Still not working :( |
Hi, I got the same issue with 25.0.4, i've change the timeout to "7200" to the both NC and the timeout error is gone but i got new error "Error when assembling chunks, status code 504" Best regards |
How to use GitHub
Steps to reproduce
Expected behaviour
The file should be uploaded sucessfully
Actual behaviour
cURL error 28: Operation timed out after 30000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Server configuration
Operating system:
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-66-generic x86_64) running docker-ce v20.10.5 build 55c4c88
Web server:
Database:
mysql v8.0.22 for Linux on x86_64 (MySQL Community Server - GPL)
PHP version:
The one used in nextcloud docker container (PHP 7.4.14 (cli) (built: Jan 7 2021 17:26:34))
Nextcloud version: (see Nextcloud admin page)
Nextcloud 20.0.8
Updated from an older Nextcloud/ownCloud or fresh install:
Well I'm running this nextcloud instance since two or three major versions, I think.
Where did you install Nextcloud from:
I'm using the official docker image with this custom Dockerfile (to add smbclient):
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser:
Chromium Version 89.0.4389.82 (Offizieller Build) Arch Linux (64-Bit)
Operating system:
Manajaro Linux 5.4.101-1-MANJARO
Logs
Web server error log
Web server error log
There are some SMB errors in it as well that are not relevant to the issue. I'm working on it ;)
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The javascript console log (removed all jquery deprecation warnings)
The network log (the request that failed)
Additional information
This problem does not occur when uploading to an owned federation share or anywhere else.
We also tried it the other way around (I created the federation share and someone else tried to upload the same file, which has not worked either (same error)). He uses the same nextcloud version and Firefox on Windows as client browser.
We've also set our PHP upload limits to some gigabytes. This is my custom-php.ini:
The text was updated successfully, but these errors were encountered: