Opened 13 years ago

Last modified 12 years ago

#5701 new Bug report

Uploading large file fails, strange progress bar behavior

Reported by: Banana Owned by:
Priority: normal Component: FileZilla Client
Keywords: upload, progress bar Cc: hnorobertson@…
Component version: Operating system type: Windows
Operating system version: Win7 Professional 64-bit


I've seen this problem with several servers: when uploading a large file (e.g. 20 MB), FileZilla seems to starts uploading and then it's instantly at 100% (upload speed specifying 10 or 20 MB/s which isn't even possible with my connection).

Then it waits for a while (I think it is now in fact uploading actual data, even though it indicated it was already at 100%).

Then after a while it either says it's finished, but the file is uploaded only partially most of the time. Or it says "are you sure want to overwrite?" and then showing a smaller destination file (which didn't exist previously), i.e. it uploaded the file partially and now wants to restart, asking to overwrite the existing remote file (remote file = the part which it just uploaded).

Here's an FTP account in which I can reproduce this problem almost every single time:

host = ftpes://
name = test86413
pasw = Test123
server type: FTPES (explicit TLS/SSL) (using default port 21)

I've just tested again with v3.3.5 (windows client), and it happened every attempt when I upload a 20 MB file.

I've seen this before with other servers as well, but this is the first time it occurs on a server on which I can easily make a test account for you to debug with.

Hope this helps!!

Change History (1)

comment:1 by Hamish Robertson, 12 years ago

Cc: hnorobertson@… added
Priority: criticalnormal

Switching to active mode seems to be the best work around. Because of this I'm guessing it's a firewall/router configuration issue. I'm on a university network at the moment so can't test.

An alternative work-around is to increase or disable the timeout. This will allow the upload to complete but the progress bar will still not function correctly.

Note: See TracTickets for help on using tickets.