Opened 16 years ago
Closed 8 years ago
#4425 closed Other (outdated)
FTP connections stop working; Error, could not connect to server
| Reported by: | geeklani | Owned by: | |
|---|---|---|---|
| Priority: | high | Component: | FileZilla Server |
| Keywords: | cannot connect, server interface, error | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | 2003 Server |
Description
I have been running FileZilla server for 2 years now. I recently ran into problems with it not working. This is the error I get when I try to connect to the server via the server interface.
FileZilla Server version 0.9.31 beta
Copyright 2001-2009 by Tim Kosse (tim.kosse@…)
Connecting to server...
Error, could not connect to server
Trying to reconnect in 5 seconds
When this happens, no clients can connect to the server. I never received this message until a month ago or so. An upgrade to 0.9.31 beta would not fix the problem. I am running Windows 2003 Server. No changes have been made to the server except for automatic windows updates, I didn't see anything that would affect a running FTP process/service. I am at a loss, there is nothing in any log files or any other evidence to point us in a direction. There is no antivirus or firewall software on the computer, the network is behind a firewall. If I want to test without any firewall I would just connect locally from another machine in the same network. So the firewall is not an issue.
Change History (19)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Status: | new → moreinfo |
|---|
Have you checked the Windows Firewall? It has the habit of turning itself on again after visiting Windows Update.
comment:3 by , 16 years ago
| Status: | moreinfo → new |
|---|
Yes, it is disabled, I even turned it on and then back off.
comment:5 by , 16 years ago
| Status: | moreinfo → new |
|---|
Yes the service is running, even when it's not accepting any connections. A restart of the service when it breaks does nothing.
comment:6 by , 16 years ago
| Status: | new → moreinfo |
|---|
Check with netstat -a -b -n if the service is listening on the administration port of if it's in use by some other program.
comment:7 by , 16 years ago
| Status: | moreinfo → new |
|---|
Running that command both when the server is working gives:
TCP 127.0.0.1:14147 0.0.0.0:0 LISTENING 1128
[FileZilla Server.exe]
TCP xxx.xxx.xxx.xxx:21 0.0.0.0:0 LISTENING 1128
[FileZilla Server.exe]
It just did it again, ran fine for 2 days then get:
Error, could not connect to server
Trying to reconnect in 5 seconds
Reconnecting to server...
when trying to access the admin interface, FTP connections cannot be made.
comment:9 by , 16 years ago
| Status: | new → moreinfo |
|---|
How many user and group accounts do you have? How many successful logins each day do you have?
comment:10 by , 16 years ago
| Status: | moreinfo → new |
|---|
There are 45 users, no groups. The number of logins per day varies, sometimes it can be 200-300 or 100, it can crash after 1 day of usage or 3. It's random yet no evidence to say why it stops working.
comment:11 by , 16 years ago
Logins/day seems fine, if I'm working heavily on FZ I have more on some days and I can use the server for weeks without a restart.
I'll try and let the server run in a debugger and hammer it with a bunch of scripts all night long, with some luck I can reproduce it.
comment:12 by , 16 years ago
It used to run for months without a reset, it would never crash. I thought it was maybe the connections but it isn't being hit too hard. The ID number in every log file entry sometimes hits 500 or 2000, so there's no pattern there.
comment:13 by , 16 years ago
| Status: | new → moreinfo |
|---|
Do you have any IP address filters set?
Do you use autoban?
comment:14 by , 16 years ago
| Status: | moreinfo → new |
|---|
There are no IP address filters and autoban is not enabled.
follow-up: 16 comment:15 by , 15 years ago
| Priority: | normal → critical |
|---|
I experience the same situation !
I've installed it on a W200 and accessing it from a vista home premium.
On server I've configured port 11712 for authenticating and 51712 for data transfer.
21712 is for UI
Than I've opened on both sides IP security and routers to allow WAN to LAN port 11712 and 51712.
Filezilla Client was setup to passive and I got nicely a connection on desired ports...
Now, after a day, tried few minutes ago to connect again, but it looks server is not responding to connection requests...
I've checked all the settings but all are the same.
Now I've tried to uninstall the server and see what happen.
But it said :
There are other users logged on to this computer
If you uninstall this program while another user is running it the program might not uninstall completely.
no users reported by server UI.
Please advice me what can I do ?
FZC said:
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
With kind regards
comment:16 by , 15 years ago
| Priority: | critical → normal |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
my problem was a firewall setting and a windows 2003 temporary erro...
comment:17 by , 12 years ago
| Priority: | normal → high |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Type: | Bug report → Other |
I have the same issue as geeklani and I have upgraded to 0.9.41 but it cannot help to fix the problem. It seems the case has been closed but I don't see any solution regarding this issue. Please advice the solution on this issue.
comment:18 by , 8 years ago
Triage suggestion
The Windows operating systems mentioned in this bug report are no longer supported by Microsoft (Windows Server 2003 extended support ended in 2015 and Windows Vista extended support ends in a few days). In addition, this report is eight years old.
I suggest closing this bug report.
comment:19 by , 8 years ago
| Resolution: | → outdated |
|---|---|
| Status: | reopened → closed |
In addition, the server will run for several hours before having this problem. The only way to fix it is to reboot the machine. Restarting the FZ service doesn't fix it.