Core FTP

In the site profile - Advanced - External - Post download

field you can call an external program to send emails.

Will investigate the AWS smtp issue...

Getting your build updated to something more recent will likely solve the issue.

There have been keypair issues fixed since this build, starting with build 673 there are key pair updates.

Additionally, if you have a log of the connection attempt, that may be helpful.

Did you run the .exe in the GUI? The version you are using may be expired (this only applies to the mini-server, to encourage installing updates).

Updates from Core FTP Server build 775

Detected vulnerability fixes as described in:
https://coreftp.com/forums/viewtopic.php?t=4053639

Fixes will be in 2.37

Although this is detected as a vulnerability in the mini server, no functionality was allowed without a verified, logged in user.

For those concerned, this was fixed in Core FTP Server in 2018.

Standard has the multi-connection options. Make sure you install your license as administrator.
https://coreftp.com/license.html

You do need to install the Pro version over the LE version for these options though.

Partial log as follows: sftp -v test-ed25519@10.0.0.137 OpenSSH_8.9p1 Ubuntu-3ubuntu0.13, OpenSSL 3.0.2 15 Mar 2022 debug1: Connecting to 10.0.0.137 [10.0.0.137] port 22. debug1: Connection established. debug1: identity file /home/test/.ssh/id_ed25519 type 3 debug1: Local version string SSH-2.0-Open...

Which build of Core FTP Server and Linux are being used?

Tested this with Core FTP Server 775 and Ubuntu22 without issue.

Update: Use port 587 with the TLS 1.2 option checked.

Try port 587, with the "TLS 1.2" option checked (no other options checked)

-----

Post the log if you have it.

The most common solution is disabling the pipelining option under Advanced -> SSH

in your site profile.

Some servers will not allow multiple connections (or can't handle it in some cases).

If you post the full log there might be more information that helps diagnose the issue.

Better to always start with one connection, then work up from there.

use "runas" or psexec to specify the account you setup under.

view - options - data - use the following configuration file

Uncheck this option in your site profile, Advanced -> SSH -> Use Pipelining.

------

currently there is only the "FIPS mode" option, which will prevent most outdated algorithms/ciphers from being used..

Will look into the possibility of being able to select ciphers

In the domain setup under "Disable FTP" - "..." there are options to disable SSL and check TLS versions to use. Changes go into effect next server restart.

--------

Cumulative updates from builds 772-774

Additional speed improvements

A fix for this issue will be build 775.

To get around this issue, "Start" Core FTP Server and then registration should proceed to work correctly.

If this does not work, contact support for the stand-alone registration utility

---------------

--------------------

--------------------

It looks like the client may have aborted the transfer as a disconnection was likely the reason for the abort of the transfer by Core FTP Server.

Would check the client for any potential error messages that may help diagnose the issue.

----------------

----------------------

---------------------

Uncheck the "PASV" command in your site profile

The mini server does *not* utilize libssh - it is not used in Core FTP mini server

What would be needed is a test demonstrating that the same issue occurs with the mini server to verify this issue actually exists.

This looks to be a libssh issue and may not apply to Core FTP software.

If there is an example of this bypass, please forward to feedback at coreftp.com

-key <c:\path\keyfilename>

In looking at the error it looks like the site profile is not being found as the hostname isn't correct. If you switch to "file based storage" it will likely alleviate these issues.

https://coreftp.com/forums/viewtopic.php?t=4022670

Build 770 may fix this issue that was introduced in build 761.

Cumulative updates from builds 764-770

Fixes an error introduced in 2.34 that may have caused stat issues for some clients.

The user may be exceeding the "max conns per IP" setting. You can increase it on a per user basis in the user's "general" - "limit # of logins" setting.

There is also the "Always allow login" option also but use with caution.

----------

A recent test with the import function reveals some issues that are fixed as of build 769.

-----------------------

---------------

Search found 985 matches