Hello,
I have a server that is currently running Filezilla on port 21 for regular FTP and CoreFTP server on port 22 for SSH FTP for secure transactions. Prior to upgrading to Build 369 I was able to run both side by side without issue. Now after upgrading CoreFTP keeps attempting to take over port 21, which disables Filezilla.
If I login and start CoreFTP manually I receive the following error on starting the server:
The socket binding to local port failed. (port 21)
Filezilla continues to work on port 21. CoreFTP works on port 22 as expected.
When I stop the server it shows the following:
Shutting down server...(server.domain.com -ftp)
Shutting down server...(server.domain.com -ssh)
So it appears that CoreFTP server is attempting to run the regular FTP server.
Going into the Setup for the domain and Disabling FTP has no affect.
Now this is all workable if I am logged into the server, however if I start CoreFTP Server service Filezilla immediately stops working. Telnet to port 21 shows CoreFTP answering the call.
The readme says " The FTP protocol is on by default. Select the "Disable FTP" option in the domain setup if you do not want to run FTP or SSL in a domain (ie: only wish to run SSH/SFTP or HTTPS)"
But that does not seem to work. Can I manually modify the config.dat to get CoreFTP server to stop running as a regular FTP server. I only wish to run SSH/SFTP but I cannot seem to make that happen?
Regards
Cannot disable FTP build 369
-
- Site Admin
- Posts: 987
- Joined: Mon Mar 24, 2003 4:37 am
-
- Site Admin
- Posts: 987
- Joined: Mon Mar 24, 2003 4:37 am