Custom Query (8096 matches)
Results (145 - 147 of 8096)
|#9901||wontfix||FileZilla gives erroneous failed message|
I have a very large file -- 320+MB -- and when I upload it to our FTP Side, after about 30-45 minutes, it ALWAYS ends on the Failed Transfers list with the reason "could not start transfer."
This error is (a) obviously erroneous as it just uploaded the file. I can verify this by first deleting the version on the site and then uploading a new version. When it's done uploading the new version is there; and (b) it didn't actually fail because if I download the file (which is a signed exe) it passes all integrity checks and its signature is still intact which it wouldn't be if it had failed.
If you'd like to grab the file to play with it's at:
|#10838||rejected||FileZilla client checks for updates, even with "Check for FileZilla updates automatically: Never"|
v3.16.1 gives an update for 220.127.116.11, even with the "check for update"-setting disabled. I am often abroad on a mobile pay-per-byte connection, and both dialog and mobile data costs pretty annoying.
I am aware of the general rule to install the latest version and try again before reporting the bug, which would ofcourse ' ' ' solve ' ' ' the problem as in not showing that there's a newer version.
My config (relevant sections):
release 18.104.22.168 http://downloads.sourceforge.net/filezilla/FileZilla_22.214.171.124_win64-setup.exe 6513888 sha512 4d5e5d426af9dd689cb8c070d528c849719dc18544de194475bf3a0f5e35f8c9d449749fb2074a68292579b267ee2b23d1e2b31bae20d7185aa44061cca6981c
126.96.36.199 (2016-05-09) ... I removed 'whatsnew' items for bug report brevity ... </Setting>
When attempting to upload using FileZilla the server access does not list the directories. Unable to list directories is the error. At first I thought it was my problem then discovered after the update from my older version (188.8.131.52) is when the problem began. I rolled back to the 184.108.40.206 version and the app began to work correctly. I now ignore the prompt to update each time it loads. I have other clients that use FileZilla and I recommend to them not to update until further notice about this problem being solved.