Download of large files fails #28
Comments
|
application.properties was used in older versions. You should set the limit from the settings in the admin dashboard |
|
The limit is at 100GB and I can easily upload files thar are larger than 1GB. Only the download stops after about 1GB without finishing. 
|
|
After some more tests, I got a similar issue but with much larger files, much later in the download process and I don't know if it's connected but will update here if I manage to fix it so you can try again |
|
I played around with the reverse proxy settings (using Nginx Proxy Manager). Setting proxy_max_temp_file_size to the max. filesize did the job. I am not that much into the file transfer mechanics, but is it normal that a reverse proxy has to buffer the whole response? I thought responses are split into chunks or something. |
|
Hey! Yeah, the app handles the file in chunks, but it looks like Nginx tries to buffer the whole file before sending it to the client, which is probably what's causing the error you're seeing. In the next update, I’ve added a header to tell Nginx not to buffer before sending the file, so that should fix the issue. If it still happens, let me know and I’ll figure out another solution! In the meantime, you can also disable buffering in the Nginx config instead of increasing the limit. |
|
You can try 1.4.0 to see if it's fixed. |
|
Doesn't work: situation is the same with version 1.3.0. |
|
Ok it's worse actually. proxy_buffering on; Isn't working with v1.4.0. It just stops after 1GB. |
|
Try without any of the nginx settings
…On Fri, Mar 21, 2025, 01:17 SpiGAndromeda ***@***.***> wrote:
Ok it's worse actually.
proxy_buffering on;
proxy_max_temp_file_size 20480m;
Isn't working with v1.4.0. It just stops after 1GB.
—
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALKAUL4AFFJD6WD556EKAGL2VNEBHAVCNFSM6AAAAABYHYAARKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBRHA3DMMJZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: SpiGAndromeda]*SpiGAndromeda* left a comment
(RoastSlav/quickdrop#28)
<#28 (comment)>
Ok it's worse actually.
proxy_buffering on;
proxy_max_temp_file_size 20480m;
Isn't working with v1.4.0. It just stops after 1GB.
—
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALKAUL4AFFJD6WD556EKAGL2VNEBHAVCNFSM6AAAAABYHYAARKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBRHA3DMMJZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I just uploaded a 7GB large file to my Quickdrop instance. It's shown in the admin panel, I can start the download and I can also fetch the file manually from the server filesystem.
The download breaks after about 1GB.
This is the cruacial part of the logile. As you can see, I already restarted the application (recreated the container)
This is the docker compose configuration:
I already created a application.properties file:
Smaller files can be downloaded without problems. Other files larger 1GB result in the same problems.
The text was updated successfully, but these errors were encountered: