Hello,
half a year ago I installed FileZilla Server 0.9.41 Beta on a Windows Server 2003 SP2 (32 Bit)
I set a password for the FileZilla Server Interface and did some settings for FTP.
All was right.
This morning, when controlling the server, I checked if there was an update for FileZilla Server and noticed that there is a download 0.9.41 (NOT MENTIONED BETA), so I thought it is the final and installed it.
Unfortunately this is a mistake, it is still the 0.9.41 BETA, so it was absolutely in vain to "update".
But after this "update", I could not anymore login into the Server Interface, I get:
"Error, could not connect to server"
The credentials were still the same, so I wonder.
What did I do wrong?
Do I need to restart the Windows Server?
The FileZilla Server is running though, on port 21 I can see him.
frank
After Update - could not connect to server
Moderator: Project members
Re: After Update - could not connect to server
A final version will probably start with 1.00, I guess.so I thought it is the final
Did you change the admin port during installation (first or second)? The installer will set that port back to its default (14147) unless you change it. Does FZ Server listen on 14147? If yes, try connecting to that port with the interface.What did I do wrong?
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: After Update - could not connect to server
Yes! That was my error! I had changed the Port instantly to 11111 when I first installed it.boco wrote:...Did you change the admin port during installation (first or second)? The installer will set that port back to its default (14147) unless you change it. Does FZ Server listen on 14147?...
Now all works again, leaving the port to 14147.
Thanx you muchly!
frank