Uploads of files >1GB doesn't work

Hey,
for some reason I always get this error message when I try to upload files bigger than 1gb. https://gyazo.com/eec63c0e66f2813dfd65f74245c14c0a

in conf/seafile.conf I already set
[fileserver]
max_upload_size=20000

in nginx.conf i set
client_max_body_size 20G;

in nginx/seafile.conf
i set client_max_body_size 20G;

in php.ini i set
post_max_size 0
upload_max_filesize 20G

yet it can’t even upload files bigger than 1GB (even though it’s set to 20GB)
It neither works using the web interface nor the client…

Can someone pls help me?

Do you use apache or nginx as a reverse proxy? then you have to adjust a timeout value

Nginx
I guess I use the default one but I’ll check it later

Test different values in /etc/nginx/nginx.conf:

proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;

https://pastebin.com/bCKdTFWu
https://pastebin.com/fP8bGS8q

got the configs like this now, before the timeouts were set to 3600s in the /etc/nginx/sites-available/seafile.conf
however it still doesn’t work

in your nginx.conf:

send_timeout  10;

in your seafile.conf.

send_timeout  600;

I don’t know which value is used by nginx.

Hey,
try this:

proxy_request_buffering off;

I am having similar problems with the android app, it crashes when it tries to sync a file larger than 1gb.

I have max_upload_size=0 declared on conf/seafile.conf. I haven’t checked the nginx conf though.

EDIT:

client_max_body_size 0; is declared under /seafhttp

I didn’t try Garlied’s approach yet. But while checking the nginx error logs i noticed this https://pastebin.com/aw0NStzR

but how would i fix this? (maybe Garfield’s idea does the job dunno yet)

that does not work :confused:
https://pastebin.com/EVKVYVYQ

which one would be better ?

i now checked the console in the web browser, it gives me different errors…

clicking on the: “400 (Bad Request)”: Screenshot - 7ce2489ddcf2b0f368d01ffb2bb24e54 - Gyazo → Header: Screenshot - d461f67a26047af53a1ab2622a2f9884 - Gyazo

clicking on the: “502 (Bad Gateway)”: Screenshot - f877b3704cbb0a7406ec7157f2724f5e - Gyazo → Header: Screenshot - 3446d6bb14fdd404a92538eeb57c0094 - Gyazo

clicking on the: “net::ERR_CONTENT_LENGTH_MISMATCH”: Screenshot - 8226e5363f29e552aaf17bbaea5aa94e - Gyazo → Header: Screenshot - 6ea4d45a1b0812fcbb946f56423b58cc - Gyazo

Come on… Someone has to know some way to fix this…