#4460 closed Bug report (fixed)
FileZilla Client retry too fast during data transfer
| Reported by: | smallasia | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | login retry too fast | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | Windows XP SP3 |
Description
In FileZilla Client, there is an option:
Settings -> Connection -> Reconnection settings -> Delay between failed login attempts
When I connect to the FTP server this option is effective for the control connection. However after the connection established and file is being downloaded, this option seems to be ignored for the data connections.
If the server activated anti-hammering protection and limited the maximum number of simultaneous logins I will immediately being banned.
FileZilla version tried: ANY version, even the latest 3.2.4 (as of 27th APR 2009)
Sample log:
(The example below used TLS connection, Maximum number of retries: 2, Delay between failed login attempts: 5)
16:55:33 Status: Connecting to [server ip]:21... 16:55:33 Status: Connection established, waiting for welcome message... 16:55:33 Response: 220 FTP server ready. 16:55:33 Command: AUTH TLS 16:55:33 Response: 234 AUTH Command OK. Initializing SSL 16:55:33 Status: Initializing TLS... 16:55:33 Status: Verifying certificate... 16:55:33 Command: USER [username] 16:55:33 Status: TLS/SSL connection established. 16:55:33 Response: 331 User name received, need password. 16:55:33 Command: PASS ******** 16:55:33 Response: 230 Ok 16:55:33 Command: CLNT FileZilla 16:55:33 Response: 200 Noted. 16:55:33 Command: OPTS UTF8 ON 16:55:33 Response: 200 UTF8 ON 16:55:33 Command: PBSZ 0 16:55:33 Response: 200 PBSZ Command OK. Protection buffer size set to 0. 16:55:33 Command: PROT P 16:55:33 Response: 200 PROT Command OK. Using Private data connection 16:55:33 Status: Connected 16:55:33 Status: Retrieving directory listing... 16:55:33 Command: PWD 16:55:33 Response: 257 "/" is working directory. 16:55:33 Status: Directory listing successful 16:55:43 Status: Retrieving directory listing... 16:55:43 Command: CWD downloads 16:55:43 Response: 250 CWD Command successful. 16:55:43 Command: PWD 16:55:43 Response: 257 "/downloads/" is working directory. 16:55:43 Command: TYPE I 16:55:43 Response: 200 Type set to I. 16:55:43 Command: PASV 16:55:43 Response: 227 Entering Passive Mode ([server ip],9,152). 16:55:43 Command: MLSD 16:55:44 Response: 150 File status okay; about to open data connection. 16:55:44 Response: 226 Closing data connection. 16:55:44 Status: Directory listing successful 16:56:00 Status: Connecting to [server ip]:21... 16:56:00 Status: Connection established, waiting for welcome message... 16:56:00 Response: 220 FTP server ready. 16:56:00 Command: AUTH TLS 16:56:00 Response: 234 AUTH Command OK. Initializing SSL 16:56:00 Status: Initializing TLS... 16:56:00 Status: Verifying certificate... 16:56:00 Command: USER [username] 16:56:00 Status: TLS/SSL connection established. 16:56:00 Response: 331 User name received, need password. 16:56:00 Command: PASS ******** 16:56:00 Response: 530 Maximum number of simultaneous logins reached 16:56:00 Error: Could not connect to server 16:56:00 Status: Connecting to [server ip]:21... 16:56:00 Status: Connection established, waiting for welcome message... 16:56:00 Response: 220 FTP server ready. 16:56:00 Command: AUTH TLS 16:56:00 Response: 234 AUTH Command OK. Initializing SSL 16:56:00 Status: Initializing TLS... 16:56:01 Status: Verifying certificate... 16:56:01 Command: USER [username] 16:56:01 Status: TLS/SSL connection established. 16:56:01 Response: 331 User name received, need password. 16:56:01 Command: PASS ******** 16:56:01 Response: 530 Maximum number of simultaneous logins reached 16:56:01 Error: Could not connect to server 16:56:01 Status: Connecting to [server ip]:21... 16:56:01 Status: Connection established, waiting for welcome message... 16:56:01 Response: 220 FTP server ready. 16:56:01 Command: AUTH TLS 16:56:01 Response: 234 AUTH Command OK. Initializing SSL 16:56:01 Status: Initializing TLS... 16:56:01 Status: Verifying certificate... 16:56:01 Command: USER [username] 16:56:01 Status: TLS/SSL connection established. 16:56:01 Response: 331 User name received, need password. 16:56:01 Command: PASS ******** 16:56:01 Response: 530 Maximum number of simultaneous logins reached 16:56:01 Error: Could not connect to server
Change History (3)
comment:1 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 15 years ago
| Keywords: | login retry too fast added |
|---|
Thank you for your response!
I just tried out the latest 3.2.4.1 version and it is fixed.
I noticed that you have mentioned "If FileZilla would strictly follow the specifications, it wouldn't retry at all in this case." However 3.2.4.1 still connected 3 times before giving up. Actually it is okay for me, I just want to notify you about this behavior. Thank you.
Log while downloading files:
19:03:25 Status: Connecting to [server ip]:21... 19:03:25 Status: Connection established, waiting for welcome message... 19:03:25 Response: 220 FTP Server ready. 19:03:25 Command: USER [user name] 19:03:25 Response: 331 Password required for [user name] 19:03:25 Command: PASS ******** 19:03:25 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:03:25 Error: Could not connect to server 19:03:25 Status: Delaying connection due to previously failed connection attempt... 19:03:30 Status: Connecting to [server ip]:21... 19:03:30 Status: Connection established, waiting for welcome message... 19:03:30 Response: 220 FTP Server ready. 19:03:30 Command: USER [user name] 19:03:30 Response: 331 Password required for [user name] 19:03:30 Command: PASS ******** 19:03:30 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:03:30 Error: Could not connect to server 19:03:30 Status: Delaying connection due to previously failed connection attempt... 19:03:35 Status: Connecting to [server ip]:21... 19:03:35 Status: Connection established, waiting for welcome message... 19:03:35 Response: 220 FTP Server ready. 19:03:35 Command: USER [user name] 19:03:35 Response: 331 Password required for [user name] 19:03:35 Command: PASS ******** 19:03:35 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:03:35 Error: Could not connect to server
Log while starting a connection:
19:08:05 Status: Connecting to [server ip]:21... 19:08:06 Status: Connection established, waiting for welcome message... 19:08:06 Response: 220 FTP Server ready. 19:08:06 Command: USER [user name] 19:08:06 Response: 331 Password required for [user name] 19:08:06 Command: PASS ******** 19:08:06 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:08:06 Error: Could not connect to server 19:08:06 Status: Waiting to retry... 19:08:11 Status: Connecting to [server ip]:21... 19:08:11 Status: Connection established, waiting for welcome message... 19:08:11 Response: 220 FTP Server ready. 19:08:11 Command: USER [user name] 19:08:11 Response: 331 Password required for [user name] 19:08:11 Command: PASS ******** 19:08:11 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:08:11 Error: Could not connect to server 19:08:11 Status: Waiting to retry... 19:08:16 Status: Connecting to [server ip]:21... 19:08:16 Status: Connection established, waiting for welcome message... 19:08:16 Response: 220 FTP Server ready. 19:08:16 Command: USER [user name] 19:08:16 Response: 331 Password required for [user name] 19:08:16 Command: PASS ******** 19:08:16 Response: 530 Sorry, the maximum number of clients (1) from your host are already connected. 19:08:16 Error: Could not connect to server
Note:
See TracTickets
for help on using tickets.
Will be fixed in the next version.
Note that your server is using the wrong reply code, 5yz codes are permanent errors. If FileZilla would strictly follow the specifications, it wouldn't retry at all in this case.