Coreftp Lite

[Nayra Waddles]

Iam using an FTP server (using CoreFTP) on Windows Server 2019. Currently I am setting up the certificates yearly on renewal that is done manually. Is anyone aware of a way to have this auto renew like we have done with winacme with an IIS server?

I was previously using GoDaddy that we would get a yearly SSL certificate an apply it to our servers. We moved all our webservers to using lets encrypt, but coreFTP is not a web application and does not use IIS/apache/etc. I was wondering if there was a way for me to be able to auto-renew the certificate for coreftp somehow with lets encrypt.

OK.

You don't require IIS to obtain, nor renew, an LE certificate.

You can use one of several Windows ACME clients [in --standalone mode] to validate the HTTP authentication requests.

[winacme is one of those]

I've gone to above site and for Windows all I'm seeing is binding to IIS. It has to be a complete standalone setup to renew the cert.. and the config in CoreFTP needs to be able to point to this certificate.

You then need to set that file information in the CoreFTP server settings and if you keep the same path for certificate renewals then picking up the new/renewed certificate should just involve restarting the CoreFTP server.

If you are already familiar with win-acme you should use that to get your FTP certificate, just use the self-hosting option (which will spin up a temporary http listener to complete the http challenge, you will need TCP port 80 open).

I note that the CoreFTP website itself has no SSL configured and they haven't had a new release since 2017 so I'd take that as a sign you should probably look at other FTP server options sooner rather than later.

It is recommended that you first go into the site manager and create a site profile. While it is not required that you use a site profile via command line, it is strongly recommended for security reasons (to protect your user and password). For more examples without a site profile, check the help file topic 'command line' from within Core FTP.

Once you have verified that your site profile connects and lists the remote directory correctly from within the GUI, you can then be assured that command line transfers will work with your site profile.

Site profile not found errors - Make sure the user account calling Core FTP is the same one that created the site profile.

If this is not an option available to you, you can setup Core FTP to have site profiles available to all user accounts.

To have all user accounts access site profiles, there are two options.

1: Export Site profiles (right click list of sites in the Site Manager) to a file, then call coreftp.exe -importglobal

This will put the exported site profiles into the global registry (available to most user accounts by default - only applies to older versions of Windows).

2: Use file based storage (View -> Options -> Data -> Use default configuration file.

Site profiles will need to either re-entered or you can call coreftp.exe -import to import them ("Run as administrator" when setting this option).

You'll want to use passive FTP instead of active - passive is able to traverse NAT since the client will initiate both the command and data connections to the server, instead of relying on the server to initiate the data connection which will be blocked by eero's firewall.

Thanks for the info. But how we specify active passive when I am connecting to FTP server through windows explorer? I even tried from external website using coreftp with passive option and the FTP connection establishes. It is the data connection says time out to get the root directory. It says time out. I even increased the time, but no luck. I saw on internet and no perfect solution I found in regards to Eero devices.

Some more info from LAN. the computer connected to same subnet. I connected to the NAS drive through Coreftp and also on windows explorer. But externally it did not work. I will furnish those screenshots as well.

3a8082e126