421 too many connections (8) from this ip – FileZilla fix

Written by Avesta Sabetian Wednesday, 19 August 2009

Related documents:
[1] Installing FileZilla FTP Client

This blog entry is an overview on how to fix the following error in your FTP client:

421 too many connections (8) from this ip

This may sometimes be accompanied with a “Delaying connection for 5 seconds due to previously failed connection attempt” error.

We will be using FileZilla in this example. If you do not know FileZilla or how to use it, we recommend reviewing our blog entry on How to install FileZilla .

Lets start, open up FileZilla, and click on “File” on the top left and then click on “Site Manager”:

2) Once inside SiteManager:

If the site doesn’t already exist in the list: click “New Site” and fill out the necessary information and continue.

Once the site exists in the list, choose it and go to the “Transfer Settings” tab:

From here, simply click on the checkmark box next to “Limit number of simultaneous connections” and you can keep “1″ in the box like such:

Thats all, now Press “Connect” on the bottom left and give it another try. If you run into any problems, simply comment here and we’ll get you helped.

23 Comments

1. selva   |  Tuesday, 20 October 2009 at 3:31 am

   Thanks For your step by step explanations.Follow your step, i am fixed that error.

   
2. Ken   |  Sunday, 01 November 2009 at 1:21 pm

   I tried that and I still get the 421 Too many connections (4) from this IP error.

   
3. Arvand Sabetian   |  Sunday, 01 November 2009 at 8:26 pm

   You may need to completely shut things down so the previous connections are killed.

   
4. How to Install Filezilla Client | Arvixe Blog   |  Sunday, 22 November 2009 at 3:08 am

   [...] Related documents: [1] 421 too many connections (8) from this ip – FileZilla fix [...]
5. Saurabh   |  Tuesday, 23 March 2010 at 8:18 pm

   Dear member’s,

   Getting this same problem when i am connecting my FTP, it stops at MLSD

   230-Your bandwidth usage is restricted
   Response: 230-User share127 has group access to: 150
   Response: 230-OK. Current directory is /
   Response: 230 114 Kbytes used (0%) – authorized: 51200 Kb
   Command: PBSZ 0
   Response: 200 PBSZ=0
   Command: PROT P
   Response: 534 Fallback to [C]
   Status: Connected
   Status: Retrieving directory listing…
   Command: PWD
   Response: 257 “/” is your current location
   Command: TYPE I
   Response: 200 TYPE is now 8-bit binary
   Command: PORT 10,0,0,250,4,94
   Response: 500 I won’t open a connection to 10.0.0.250 (only to 122.180.9.18)
   Command: PASV
   Response: 227 Entering Passive Mode (202,71,129,226,195,229)
   Command: MLSD

   What i have to do now to resolve this problem. Please tell me

   
6. Arvand Sabetian   |  Tuesday, 23 March 2010 at 8:20 pm

   Try turning off Passive mode and using Active mode.

   
7. Tolun Cerkes   |  Tuesday, 30 November 2010 at 7:57 pm

   Yes choosing active mode in the site manager’s transfer settings tab resolved my problem. Thank you.

   
8. Brandon Thompson   |  Wednesday, 08 December 2010 at 9:12 pm

   No matter what alterations I make to the configurations in the “Site Manager” option, my connection always times out and I can’t connect to the server. What did I miss?

   
9. Arvand Sabetian   |  Sunday, 12 December 2010 at 8:32 am

   Brandon,

   What error are you receiving?

   
10. David Ho   |  Monday, 21 February 2011 at 5:58 am

    Thanks! Exactly what I was looking for – kudos!!!

    
11. AB   |  Monday, 01 August 2011 at 5:43 pm

    Thank you, it took me a while to find this but this fixed it all. Props.

    
12. Moran   |  Monday, 19 September 2011 at 5:34 am

    I did what you wrote, but I still get this error…

    
13. Hans Simtanda Caspersen   |  Tuesday, 06 December 2011 at 11:04 am

    First i was getting a “421 too many connections (12) from this ip” error, but read and did what this page says, so now i getting a

    “Response: 200 PORT command successful
    Command: MLSD
    Respons: 425 Could not open data connection to port 49657: Connection timed out”

    What do i do?

    
14. kensoXd   |  Sunday, 11 December 2011 at 1:52 pm

    graciiiiiiiiiiiiiiiiaaaaaaaaaaaaaaaaaaaaaaaaasssssssssssssss

    
15. Ryan Harne   |  Thursday, 15 December 2011 at 5:34 pm

    Still got the problem, even on sftp & active mode… so need to drop all connections, for windows.
    >> Command Prompt
    >> ipconfig /renew

    
16. kenneth   |  Saturday, 07 January 2012 at 9:10 pm

    yes choose the active .. and the problem will solve thanks for this

    
17. Juhi   |  Tuesday, 10 January 2012 at 7:15 pm

    Even after complying with the settings suggested, I am getting the error 421. Can you please help?

    
18. Matt   |  Wednesday, 25 January 2012 at 6:34 am

    I’ve had this problem for a while, i’ve changed the settings, dropped all my connections via command prompt, limited my connections to 1 (even tho my server allows 8) and changed transfer to Active. I’m on Windows 7 Professional so any help is hugely apreciated. I’ve looked over the FileZilla forums but the support is limited and not very useful!

    
19. InsaneOne22   |  Wednesday, 01 February 2012 at 9:52 pm

    Thanks for this advice, I’m now able to deploy/retreive my website without worring about problems …

    Thanks dude !

    
20. Yan   |  Thursday, 26 July 2012 at 2:51 am

    Wow, thank you so much! This solution solved my problem. Keep up and continue sharing!

    
21. Christopher Ohlsen   |  Tuesday, 31 July 2012 at 8:22 pm

    Thanks for the info. I actually just ran into this problem and couldn’t figure it out. I found a forum where a few people had this issue and they all concurred that there was nothing that can be done about it… Just that Filezilla thinks that you are hacking if you disconnect and reconnect repeatedly which is what the client does for every file. Anyway, thanks; I implements your fix and it is running smooth now.

    
22. Chris   |  Wednesday, 14 November 2012 at 6:59 pm

    I turned off my firewall and it worked

    
23. Jay   |  Wednesday, 05 December 2012 at 9:12 am

    Just go to: Site manager……….Advanced………..Server type (In server type change what it is supposed to be, mine was Unix)
    All worked fine and this problem came just after an Flilezilla had an update……..new update nulled the server type