Custom Query (8169 matches)


Show under each result:

Results (301 - 303 of 8169)

Ticket Resolution Summary Owner Reporter
#5684 outdated Don't use external IP's for local connections Vladimir Naumoski

I think that here you should implement a way to manually enter which IP addresses should be considered as local connections. I have hosts from outside that are behind NAT and I am behind NAT too, so i will need to manually enter which IP's should be consider as local which should be consider as outside in order the passive mode to be correct for the external host and for the internal hosts. I have internal hosts that have IP's like 172.11 and etc that FileZilla interprets as external!???

I my case i have a 2 hosts that should be considered as external and only for them i will need the PASV mode - static IP to be set under: External server IP addresses for passive mode transfers: "Use the following IP (X.X.X.X)

I hope you understand my request.

#8731 rejected LIST or NLST commands behavior\reply if file not exists Vlad

Most FTP servers do not return an error for commands

LIST file.ext


NLST file.ext

if the file not exists. Reply of FileZilla server is:

200 Port command successful
550 Directory not found

Reply of SERV-U FTP server for example is:

200 PORT Command successful.
150 Opening ASCII mode data connection for /bin/ls.
226 Transfer complete.

Is there a possibility to change the server's response and did not return an error? If you can not make changes to the future version, can you to recommend changes of code to implement this behavior?

Thank you

#8322 duplicate Client cannot connect using Require explicit FTP over TLS Vlado


FileZilla Client


Build information:

Compiled for: i586-pc-mingw32msvc Compiled on: x86_64-unknown-linux-gnu Build date: 2012-11-18 Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12 GnuTLS: 3.1.4 SQLite:

Operating system:

Name: Windows XP (build 2600, Service Pack 3) Version: 5.1 Platform: 32 bit system


vsftpd-2.2.2-11.el6.i686 on CentOS 6.3 x86 configured with:

tcp_wrappers=YES pasv_enable=YES ssl_enable=YES force_local_logins_ssl=YES force_local_data_ssl=YES

CLIENT DEBUG LOG: 13:18:36 Trace: CControlSocket::DoClose(64) 13:18:36 Trace: CControlSocket::DoClose(64) 13:18:36 Status: Resolving address of 13:18:36 Status: Connecting to 13:18:36 Status: Connection established, waiting for welcome message... 13:18:36 Trace: CFtpControlSocket::OnReceive() 13:18:36 Response: 220 Welcome to FTP PB service. 13:18:36 Trace: CFtpControlSocket::SendNextCommand() 13:18:36 Command: AUTH TLS 13:18:36 Trace: CFtpControlSocket::OnReceive() 13:18:36 Response: 234 Proceed with negotiation. 13:18:36 Status: Initializing TLS... 13:18:36 Trace: CTlsSocket::Handshake() 13:18:36 Trace: CTlsSocket::ContinueHandshake() 13:18:36 Trace: CTlsSocket::OnSend() 13:18:36 Trace: CTlsSocket::OnRead() 13:18:36 Trace: CTlsSocket::ContinueHandshake() 13:18:37 Trace: CTlsSocket::OnRead() 13:18:37 Trace: CTlsSocket::ContinueHandshake() 13:18:37 Trace: CTlsSocket::Failure(-12, 10053) 13:18:37 Trace: GnuTLS alert 40: Handshake failed 13:18:37 Error: GnuTLS error -12: A TLS fatal alert has been received. 13:18:37 Trace: CRealControlSocket::OnClose(10053) 13:18:37 Trace: CControlSocket::DoClose(64) 13:18:37 Trace: CFtpControlSocket::ResetOperation(66) 13:18:37 Trace: CControlSocket::ResetOperation(66) 13:18:37 Error: Could not connect to server 13:18:37 Trace: CFileZillaEnginePrivate::ResetOperation(66) 13:18:37 Status: Waiting to retry...

SERVER VSFTPD.LOG: Mon Nov 19 14:05:00 2012 [pid 15066] CONNECT: Client "" Mon Nov 19 14:05:00 2012 [pid 15066] FTP response: Client "", "220 Welcome to FTP PB service." Mon Nov 19 14:05:00 2012 [pid 15066] FTP command: Client "", "AUTH TLS" Mon Nov 19 14:05:00 2012 [pid 15066] FTP response: Client "", "234 Proceed with negotiation." Mon Nov 19 14:05:01 2012 [pid 15066] DEBUG: Client "", "SSL_accept failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher"

HISTORY: - does not connect 3.6.0 - worked fine! 3.5.3 - does not connect 3.5.2 (and older) - worked fine!

ADDITIONAL INFO: There was no change in server configuration between trying FileZilla Client 3.6.0 and - I tried 3.6.0 this morning and this afternoon. I have not old VSFTPD.LOG with Client 2.5.3, so I'm not sure if there was same error message "no shared cipher".

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