Custom Query (8117 matches)
Results (7 - 9 of 8117)
|#12906||outdated||Cannot connect to Filezilla server|
Since last week, one of my customer cannot connect to FileZilla server. Keep in mind that it was working before.
One of her colleague is able to connect to the server on the same network and I can connect with her account on another network.
In the window, it says:
AUTH TLS 502 - Auth command is not supported. 502 - Please contact your network administrtator to enable FTPS service
What cause this issue?
|#12905||worksforme||Filezilla Error On Illegal Windows Characters|
Issue-This version of Filezilla is not handling illegal characters correctly. Previous versions have not had this specific trouble to replace illegal characters from the server while transferring to a Windows system.
The attached screenshot shows 3 files that failed transfer from server to Windows directory due to the illegal Windows character colon (:) present in the 3 files. The first transfer initiated using the filezilla preference of Automatic for FTP File Types resulted in the 3 files failing.
When I changed the Filezilla preference to Binary for FTP File Types and retried the folder download, the same 3 files failed.
This is not correct behavior and is also strange because in the Filezilla queue area the illegal character colon has been replaced with underscore. You can confirm that the illegal character exists on the server by reviewing the 2 highlighted files on the server side of Filezilla remote window.
"T:\pathfinder\199800 Fantastic Four 1_2 (Wizard).cbr" "T:\pathfinder\199800 Generation X 1_2 02 of 02 covers.cbz" "T:\pathfinder\199800 Spider-Man 1_2 (Wizard) 02 of 02 covers.cbz"
"\199800 Fantastic Four 1:2 (Wizard).cbr" "\199800 Generation X 1:2 02 of 02 covers.cbz" "\199800 Spider-Man 1:2 (Wizard) 02 of 02 covers.cbz"
Note: When I initially tried to download multiple directories that contained illegal characters, filezilla basically crashed (no further input or output from filezilla window). Filezilla needed to be closed completely and restarted in order to resume normal operations.
By trial and error I was able to figure out that the illegal characters in the directories was what Filezilla took issue with. I decided to download the files individually from the server to see if it could complete successfully and they did. (See the 3 files outside of the directories in the screenshot). So, Filezilla can transfer files with illegal characters correctly individually, but from within a directory queue Filezilla is failing to transfer correctly.
I also confirmed that the files could be downloaded successfully with the illegal characters replaced by installing WinSCP and queuing the 5 directories I tried with Filezilla. All directories were successfully downloaded using the Automatic File Type preference and the illegal colon (:) characters were replaced with %3A.
|#12898||fixed||File size is off by 10^-1 on remote directory listing over SSH|
File sizes on remove directory listing are off by 10-1.
Only files over 100MB are affected.
Example, file on local dir listing is 100MB. File is transferred successfully. File size on remote listing is 10MB
Please see attached screenshot.