Upload keeps failing on charset conversion and blocks process queue

[drTheMan]

Problem:

While trying to upload files I get the following error:
Error: Failed to convert command to 8 bit charset

FileZilla then keeps trying to upload the file every 20 seconds,
resulting in the same error over and over again, blocking the entire process queue.

Suggested Solution:

move transfer to failed transfers, and possibly build a feature that certain
characters automatically get replaced (should be a user specified setting of course).
Either way, please make sure these failed transfers don't stall a 4106 file upload at 0.1%

System info:

FileZilla version: 3.2.7.1
System (client) info: Windows Vista SP1, Pentium Dual Core T4200 (Dell Inspiron 1545)
System (server) info: Linux based NAS (Synology DS107+)

Log 1:

Error: Connection timed out
Status: Connecting to 192.168.1.101:21...
Status: Connection established, waiting for welcome message...
Response: 220 BarrieDisk FTP server ready.
Command: USER admin
Response: 331 Password required for admin.
Command: PASS *
Response: 230 User admin logged in.
Status: Connected
Status: Starting upload of C:\music_folder_path\Bad Religion - What Can You Do%.mp3
Command: CWD /music
Response: 250 CWD command successful.
Status: Retrieving directory listing...
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,101,217,11)
Command: LIST
Response: 150 Opening BINARY mode data connection for 'file list'.
Response: 226 Transfer complete.
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,101,217,42)
Command: STOR Bad Religion - What Can You Do%.mp3
Error: Failed to convert command to 8 bit charset

Log 2:

Response: 227 Entering Passive Mode (192,168,1,101,217,87)
Command: STOR Atmosphere - F!@k You Lucy.mp3
Error: Failed to convert command to 8 bit charset

Here's Ticket 849 that was closed and said to be fixed 2 years ago:

For example, my linux server uses UTF-8 as a default
charset, and my WindowsXP laptop uses CP949 (EUC-
KR) as a default charset. There should be some
charset conversion for FileZilla client to get files with
correct names, and FileZilla should be able to cope with
conversion failure.

[Tim Kosse]

Your server is broken.

Either upgrade to a proper server or refrain from using non-ASCII characters in filenames.

Please read ​http://wiki.filezilla-project.org/Character_Set for details.

[drTheMan]

Just to make a suggestion: even though you are probably right that my ftp server is causing the problem, it would be good if filezilla could cope with a situation like this.

Maybe filezilla could be able to recognize a transfer that's not gonna happen and move it to 'failed'?

[Tim Kosse]

You can already set a specification violating encoding through the site manager.