Opened 13 years ago
Closed 12 years ago
#7775 closed Bug report (outdated)
too many connections
| Reported by: | mjreine | Owned by: | |
|---|---|---|---|
| Priority: | high | Component: | FileZilla Client |
| Keywords: | session limit, sessions | Cc: | xaminmo@… |
| Component version: | Operating system type: | Windows | |
| Operating system version: |
Description
my web host, pacifichost.com supports 6 concurrent connections. Ive tried filezilla and like it but one thing is making me switch to smartftp...
Status: Connection established, waiting for welcome message...
Response: 421 Too many connections (8) from this IP
Error: Could not connect to server
Even though I set under settings - transfer
max simultaneous transfers to 4, somehow it keeps going OVER
this hard limit.
And my web host then blocks me out for about a half hour. Other ftp apps this isnt a problem. I would say this is a showstopper.
Please fix this asap.
Thanks
Change History (2)
comment:1 by , 13 years ago
| Cc: | added |
|---|---|
| Keywords: | session limit sessions added |
| Priority: | critical → high |
| Status: | new → moreinfo |
comment:2 by , 12 years ago
| Resolution: | → outdated |
|---|---|
| Status: | moreinfo → closed |
No reply for more than 28 days.
Note:
See TracTickets
for help on using tickets.
When using more than 1 session, Filezilla will have 1 for directory view/processing, plus one for each transfer. Please check netstat, or similar tool, to see for certain that you actually have zero connections to them before you start up FileZilla, and that you actually have more than 5 sessions at the time of the problem.
If that's still a problem, then please provide screenshots of the command queue showing your session, plus screenshot of the network info showing more ports.
If the problem isn't actually FzClient on your local machine, the following could be related:
If you are behind a firewall/router, and any other system on your network is connecting to pacifichost, then that will count towards your limit.
Also, if pacifichost doesn't clear disconnected sessions quickly enough, then it would count previous connections as well.
Since there is a workaround (set to one session), this cannot be critical. I'm dropping to "High" because this is still pretty important if it's proven to be an actual defect.