Custom Query (8056 matches)


Show under each result:

Results (94 - 96 of 8056)

Ticket Resolution Summary Owner Reporter
#12595 fixed Cant connect to my FTP Server trough Filezilla AdrianR

Hello, my Client got an Problem where she couldnt log in in our FTP Server it worked before but now she only gets the error Failed to connect to the server, on other PCs it worked but for her not. Is it maybe because she is using a vpn to connect to our Server and using wlan that it is too slow.

best regards Adrian Reider

#12593 wontfix pb caractère générique * et ? avec la commande mget avec la version 1.1.0 Eric MARTY

pb caractère générique * et ? avec la commande mget Depuis un client FTP sur Microsoft Windows server 2012 vers un serveur FTP FileZilla Version 1.1.0 sous Windows server 2012 lors de l'éxcution de la commande mget te*.txt j'obtiens l'erreur suivante :

R:ICMP port unreachable

425 Error reading from file: 5

#12591 fixed Filezilla returns with "504 UTF8 mode cannot be disabled" when sending an "OPTS MLST type;size;modify;perm" Fabio Alemagna Lothar

My FTP-client is trying to connect to a FileZilla server 1.0.1 that is not under my control and runs into trouble when trying to find out if MLSD/MLST is supported by the server (this is done because there are servers out there announcing support in FEAT but actually can't). Here is a snippet from the trace:

*** Opened trace file at Wed Nov 24 13:06:12 CET 2021
<-- 220-FileZilla Server 1.0.1
<-- 220 Please visit
Check UTF-8 support
---> FEAT
<-- 211-Features:
<--  MDTM
<--  SIZE
<--  MLST type*;size*;modify*;perm*;
<--  MLSD
<--  PROT
<--  PBSZ
<--  UTF8
<--  TVFS
<--  EPSV
<--  EPRT
<--  MFMT
<-- 211 End
Trying to switch to UTF-8 for control channel
<-- 202 UTF8 mode is always enabled. No need to send this command
Switch control channel to UTF-8
Check support for MLST/MLSD
MLST support is announced in features. Trying to set info-parts
---> OPTS MLST type;size;modify;perm
<-- 504 UTF8 mode cannot be disabled
Server answered MLST option request with an error, disabling feature
---> SYST
<-- 215 UNIX emulated by FileZilla.

The 504-answer lets the client fall back to use NLST which fails leading to a non-interop situation:

---> NLST *
<-- 450 No such file

So FileZilla is actually incapable of handling MLST and the error-message is wrong or there is some race condition leading to a 504 if an "OPTS UTF8 ON" is sent and another OPTS being followed directly afterwards.

Version 1.1.0 seems to have the same problem (the trace is done with 1.0.1 on the other side)

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.