EnterpriseDT Q&A - Recent questions and answers

Answered: Process Trigger authority

Sat, 15 Aug 2026 03:16:19 +0000

See this FAQ (part B). By default, process triggers run as the Windows service user (but note that you can change this in the trigger configuration [Grant permissions of ...]).

How to Ignore CRL/OCSP Validation Failures While Keeping Certificate Validation Enabled in edtFTPnet PRO 12.1.1.0?

Fri, 14 Aug 2026 04:59:50 +0000

Hi,

We're using edtFTPnet PRO 12.1.1.0 and encountering the following FTPS certificate validation error:

The certificate could not be verified:

RevocationFailure

We do not want to use:

SecureFTPServerValidationType.None

because we still want the library to validate:

Certificate trust chain

Certificate issuer

Certificate expiration

Our only requirement is to ignore CRL/OCSP validation failures when the revocation status cannot be checked.

Is there a supported way to:

Disable only CRL validation?

Disable only OCSP validation?

Ignore RevocationFailure while keeping all other certificate validation checks enabled?

Achieve this through SecureFTPServerValidationType.Callback and the ValidatingServer event?

Thanks!

Answered: Error when conneting to server via https

Fri, 24 Jul 2026 11:45:40 +0000

Please open up a support ticket here and we will assist you with this.

Answered: Chrome and Edge are failing to connect to CompleteFTP

Tue, 07 Jul 2026 08:47:19 +0000

There's a TLS 1.3 bug in versions prior to 26.1.0 that causes this issue, but it only started to affect connections after an update to OpenSSL, the TLS library used by Chrome and Edge.

The fix is to upgrade CompleteFTP to the latest version, which is 26.1.1 as of this writing.

Answered: What SSH/SFTP ciphers and encryption algorithms are supported in version 5.4.2?

Mon, 06 Jul 2026 12:38:20 +0000

There is no version 5.4.2. Could you re-check and let us know which version?

To obtain the ciphers and key exchange algorithms for any version of edtFTPj/PRO, please set debug logging to "ALL" in edtFTPj/PRO as shown here. Then please make a test connection using SSH/SFTP protocol with debug logging running. Afterwards please refer to the debug log and the test connection. All of the ciphers and key exchange algorithms offered by that version are listed in the debug log initial connection.

Answered: Roadmap for PQC support?

Thu, 02 Jul 2026 09:14:51 +0000

I have checked with the developers and they are looking to do this towards the end of the year. I can't be more exact at this time.

Answered: Does edtFTPnet/PRO support .NET 10?

Mon, 22 Jun 2026 20:48:12 +0000

Yes, it should be fine, but make sure you use the CORE DLL that is included in the distribution.

Answered: Provide home folder from database authentication to use as S3 path

Mon, 15 Jun 2026 05:29:12 +0000

Please see here in our guide. If it continues to error and you have a current support agreement in place we can assist you to troubleshoot this if you open a support ticket here.

Why internal BDH (security binary) scan highlighting vulnerability in com.enterprisedt.net.j2ssh.openssh ?

Thu, 11 Jun 2026 04:04:18 +0000

Why internal BDH (security binary) scan highlighting vulnerability in com.enterprisedt.net.j2ssh.openssh ?

Please confirm if there is any fix in latest version jar. We may take decision to purchase.

Answered: DH generator g is not in the q-order subgroup

Wed, 10 Jun 2026 18:23:22 +0000

Version 26.1.0 introduced a stricter validation of the Diffie-Hellman group parameters exchanged during SSH key negotiation. It is possible that some clients are still sending weak parameters, which is a security risk.

If your client is doing this, the easiest solution is to disable the DH group exchange methods in either the client or in CompleteFTP: diffie-hellman-group-exchange-sha1 and diffie-hellman-group-exchange-sha256. They are no longer the preferred key exchange mechanisms.

Answered: Edtftpj-pro-7.40 Please let me know OpenSSH and bouncy castle and jZlib versions used in 7.4.0 jar

Tue, 09 Jun 2026 05:46:24 +0000

edtFTPj/PRO generally does not use OpenSSH as it is a Java-based library, and OpenSSH is a separate SFTP/SSH server and client suite typically used in Unix-like systems. I will let you know the bouncy castle version once i get that information.

CompleteFTP Security Advisory 2026

Mon, 18 May 2026 15:19:13 +0000

We recently contacted customers by email regarding an important security-related matter affecting some CompleteFTP installations.

The email titled "CompleteFTP Security Advisory 2026" is legitimate and was sent by Enterprise Distributed Technologies. Customers who received the email should follow the instructions provided, including downloading and running the tool mentioned in the email.

Further technical details will be published at a later date after customers have had an opportunity to review and apply the recommended actions.

Customers requiring further information or assistance should contact us via enterprisedt.com/help.

Answered: How do I reduce the size of the events.db file?

Sun, 22 Mar 2026 22:51:37 +0000

The events.db file is a SQLite database that stores event data used by the Reports tab in the CompleteFTP Manager. It records logins, logouts, file uploads, downloads, and other activity. Over time this file can grow very large, especially on busy servers, which can eventually cause "Failed to write events data" errors.

We do plan to add auto-purging of the database as a feature, but until then the solutions below can be used.

Option 1: Delete and recreate (quickest)

If you don't need historical report data:

Stop the CompleteFTP service
Navigate to C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\Logs\
Delete events.db (and events.db-wal and events.db-shm if present)
Start the CompleteFTP service

A new, empty database will be created automatically.

Option 2: Selective purge using PowerShell

If you'd like to keep recent data while removing older records, we provide an interactive PowerShell script that walks you through the process. It shows the estimated file size for different retention periods so you can make an informed choice before deleting anything.

Download the script from our GitHub: Purge-CompleteFTPEvents.ps1

Prerequisites

The script requires sqlite3.exe, which is a free download:

Go to https://sqlite.org/download.html
Under Precompiled Binaries for Windows, download sqlite-tools-win-x64
Extract sqlite3.exe and place it in the same folder as the script

Running the script

Open an Administrator PowerShell prompt and run:

.\Purge-CompleteFTPEvents.ps1

The script will:

Locate the events.db file automatically
Show the total number of records and the date range
Offer to back up the database before making changes
Show estimated file sizes for different retention periods
Let you try different values before committing
Stop and restart the CompleteFTP service as needed

Example output

--- Analyzing database ---
  Total event records: 2,022,649
  Date range: 2025-09-19 12:16:34 to 2026-03-23 12:10:04
  Database size: 841.7 MB

--- Choosing retention period ---
  Estimated database size for different retention periods:

    Keep         Records kept   Est. size   Reduction
    ----------   ------------   ---------   ---------
    30 days           341,113   ~ 142 MB   -83%
    60 days           658,956   ~ 274 MB   -67%
    90 days           997,876   ~ 415 MB   -51%
    120 days        1,339,432   ~ 557 MB   -34%
    180 days        2,019,408   ~ 840 MB   -0%
    All             2,022,649   841.7 MB

Automated/scheduled use

For unattended use (e.g. via Task Scheduler), run with -DaysToKeep and -NonInteractive:

powershell.exe -ExecutionPolicy Bypass -File "C:\path\to\Purge-CompleteFTPEvents.ps1" -DaysToKeep 90 -NonInteractive

Option 3: Disable event recording

If you don't use the Reports feature and want to prevent events.db from growing at all:

Open the CompleteFTP Manager
Select the top-level server node
Uncheck Event recording enabled
Apply the changes

With event recording disabled, you can safely delete the events.db file while the service is stopped. It will not be recreated unless event recording is re-enabled.

Answered: Certificate will not load

Mon, 29 Dec 2025 18:51:08 +0000

The content of the private key file is actually in the PEM format, but the file-name extension is incorrect (.pvk instead of .pem). Please change the file-name extension from .pvk to .pem.

This is a regressive bug in version 25.1.0 (that wasn't present in 25.0.7), caused by a merge error. It will be fixed in the next release.

Answered: Feature Request: Delete partial files

Tue, 25 Nov 2025 22:08:12 +0000

This is usually an option left to the client, as clients typically resume the transfer with the partially uploaded file.

However, you can also configure the server to use an event to delete the partially uploaded file. Here’s an example of moving a file once it is uploaded. You could modify this to trigger only on failure and delete the file instead of moving it.

Answered: Feature Requst: Show in user list last login

Mon, 24 Nov 2025 05:22:48 +0000

Hi,

You can add a feature request here, which will go directly to the development team so that they can decide whether to add this.

Answered: Enterprise 10.0.0 offline Deactivation tells me This is not a valid Deactivation Key. Please help.

Tue, 28 Oct 2025 14:27:02 +0000

Hi,

Please open a support ticket here.

Answered: protocol error: unexpected packet type SSH_MSG_EXT_INFO

Wed, 10 Sep 2025 04:35:20 +0000

Coincidentally, we've just made a fix to edtFTPnet/PRO for this issue. If you'd like to try it out, let us know.

The FTP client has not yet connected to the server

Mon, 18 Aug 2025 04:27:17 +0000

I've seen a few posts from years ago, but I haven't seen anything recent. What am I missing? Connecting to a simple sFTP server with user/password auth, and I can list files in a directory. But when I try to check if a file exists, I receive the error that "The FTP client has not yet connected to the server. The requested action cannot be performed until after a connection has been established."

This did not happen in the previous version I was using, 10.1. It only happened once I moved to the latest version, 12.5.0.

sftp.Connect();
var remoteFiles = sftp.ListDirectory(dataDirectory);
foreach (FTPFile remoteFile in remoteFiles)
{
if (remoteFile.Dir)
continue;
// check if this file is already in another directory
string anotherName = OtherDirectoryName + remoteFile.Name;
if (sftp.Exists(anotherName )) <<<<<< problem here

EnterpriseDT.Net.Ftp.FTPException
HResult=0x80131600
Message=The FTP client has not yet connected to the server. The requested action cannot be performed until after a connection has been established.
Source=edtFTPnetPRO
StackTrace:
at EnterpriseDT.Net.Ftp.FTPClient.pE4vf83jcr(Boolean )
at EnterpriseDT.Net.Ftp.FTPClient.Exists(String remoteFile)
at EnterpriseDT.Net.Ftp.FTPConnection.Exists(String remoteFile)

The FTP component is setup with a username and password.

Protocol = FileTransferProtocol.SFTP,

ServerValidation = SecureFTPServerValidationType.None,

Log (I hope the relevant sections - I'm limited in what I can post)

DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.159 : User authentication successful
......
DEBUG [SSHFTPClient] 18 Aug 2025 01:25:13.437 : Set transfer type = BINARY
DEBUG [FTPConnection] 18 Aug 2025 01:25:13.437 : Home directory is '/home/user'
DEBUG [FTPConnection] 18 Aug 2025 01:25:13.437 : GetFileInfos('/home/user/data_qa/')
DEBUG [SSHFTPClient] 18 Aug 2025 01:25:13.437 : ResolveRemotePath('/home/user/data_qa/'); [cwd='/home/user']
DEBUG [SSHFTPClient] 18 Aug 2025 01:25:13.437 : Resolved to '/home/user/data_qa'
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.437 : Send : Name=SSH_FXP_REALPATH,Type=16,RequestID=2
DEBUG [SSH2Channel] 18 Aug 2025 01:25:13.437 : Transmit 46 bytes
DEBUG [ChannelDataWindow] 18 Aug 2025 01:25:13.437 : Remote window size decreased to 2097083
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.437 : Sent 84 bytes (NoDelay=True, SendBufferSize=65536, ReceiveBufferSize=65536)
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.437 : Packet written to socket
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.484 : FTPConnection.12 RepeatCallback received 132 bytes
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.484 : FTPConnection.12 ProcessPacket pt=SSH_MSG_CHANNEL_DATA
DEBUG [SFTPMessageFactory] 18 Aug 2025 01:25:13.484 : FTPConnection.12 CreateMessage (bufferlength=100,offset=13,length=87,type=104)
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.484 : FTPConnection.12 SSH_FXP_NAME: requestID=2, 1 files
DEBUG [SFTPMessageStore] 18 Aug 2025 01:25:13.484 : FTPConnection.12 AddMessage(2) - added to store
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.484 : Reply : Name=SSH_FXP_NAME,Type=104,RequestID=2
DEBUG [SFTPSubsystem] 18 Aug 2025 01:25:13.484 : Opening directory /home/user/data_qa
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.484 : Send : Name=SSH_FXP_OPENDIR,Type=11,RequestID=3
DEBUG [SSH2Channel] 18 Aug 2025 01:25:13.484 : Transmit 46 bytes
DEBUG [ChannelDataWindow] 18 Aug 2025 01:25:13.484 : Remote window size decreased to 2097037
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.484 : Sent 84 bytes (NoDelay=True, SendBufferSize=65536, ReceiveBufferSize=65536)
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.484 : Packet written to socket
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.531 : FTPConnection.12 RepeatCallback received 60 bytes
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.532 : FTPConnection.12 ProcessPacket pt=SSH_MSG_CHANNEL_DATA
DEBUG [SFTPMessageFactory] 18 Aug 2025 01:25:13.532 : FTPConnection.12 CreateMessage (bufferlength=26,offset=13,length=13,type=102)
DEBUG [SFTPMessageStore] 18 Aug 2025 01:25:13.532 : FTPConnection.12 AddMessage(3) - added to store
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.532 : Reply : Name=SSH_FXP_HANDLE,Type=102,RequestID=3
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.532 : Send : Name=SSH_FXP_READDIR,Type=12,RequestID=4
DEBUG [SSH2Channel] 18 Aug 2025 01:25:13.532 : Transmit 17 bytes
DEBUG [ChannelDataWindow] 18 Aug 2025 01:25:13.532 : Remote window size decreased to 2097020
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.533 : Sent 60 bytes (NoDelay=True, SendBufferSize=65536, ReceiveBufferSize=65536)
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.533 : Packet written to socket
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.582 : FTPConnection.12 RepeatCallback received 7676 bytes
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.582 : FTPConnection.12 ProcessPacket pt=SSH_MSG_CHANNEL_DATA
DEBUG [SFTPMessageFactory] 18 Aug 2025 01:25:13.582 : FTPConnection.12 CreateMessage (bufferlength=7646,offset=13,length=7633,type=104)
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.582 : FTPConnection.12 SSH_FXP_NAME: requestID=4, 39 files
DEBUG [SFTPMessageStore] 18 Aug 2025 01:25:13.582 : FTPConnection.12 AddMessage(4) - added to store
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.582 : Reply : Name=SSH_FXP_NAME,Type=104,RequestID=4
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.582 : Send : Name=SSH_FXP_READDIR,Type=12,RequestID=5
DEBUG [SSH2Channel] 18 Aug 2025 01:25:13.582 : Transmit 17 bytes
DEBUG [ChannelDataWindow] 18 Aug 2025 01:25:13.582 : Remote window size decreased to 2097003
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.582 : Sent 60 bytes (NoDelay=True, SendBufferSize=65536, ReceiveBufferSize=65536)
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.583 : Packet written to socket
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.623 : FTPConnection.12 RepeatCallback received 76 bytes
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.623 : FTPConnection.12 ProcessPacket pt=SSH_MSG_CHANNEL_DATA
DEBUG [SFTPMessageFactory] 18 Aug 2025 01:25:13.623 : FTPConnection.12 CreateMessage (bufferlength=41,offset=13,length=28,type=101)
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.623 : FTPConnection.12 ErrorCode|Status=1
DEBUG [SFTPMessageStore] 18 Aug 2025 01:25:13.623 : FTPConnection.12 AddMessage(5) - added to store
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.623 : Reply : Name=SSH_FXP_STATUS,Type=101,RequestID=5
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.623 : Send : Name=SSH_FXP_CLOSE,Type=4,RequestID=6
DEBUG [SSH2Channel] 18 Aug 2025 01:25:13.623 : Transmit 17 bytes
DEBUG [ChannelDataWindow] 18 Aug 2025 01:25:13.623 : Remote window size decreased to 2096986
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.623 : Sent 60 bytes (NoDelay=True, SendBufferSize=65536, ReceiveBufferSize=65536)
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.623 : Packet written to socket
DEBUG [PlainSocket] 18 Aug 2025 01:25:13.667 : FTPConnection.12 RepeatCallback received 68 bytes
DEBUG [SSH2Connection] 18 Aug 2025 01:25:13.667 : FTPConnection.12 ProcessPacket pt=SSH_MSG_CHANNEL_DATA
DEBUG [SFTPMessageFactory] 18 Aug 2025 01:25:13.667 : FTPConnection.12 CreateMessage (bufferlength=37,offset=13,length=24,type=101)
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.667 : FTPConnection.12 ErrorCode|Status=0
DEBUG [SFTPMessageStore] 18 Aug 2025 01:25:13.667 : FTPConnection.12 AddMessage(6) - added to store
DEBUG [SFTPMessage] 18 Aug 2025 01:25:13.667 : Reply : Name=SSH_FXP_STATUS,Type=101,RequestID=6
DEBUG [FTPConnection] 18 Aug 2025 01:25:15.785 : Exists(/home/user/data_qa/processed/checkfile.zip)

Answered: Support for v3 Putty Key Files

Wed, 13 Aug 2025 08:59:42 +0000

PuTTY v3 private keys have been supported since 11.0.0. A bug was fixed in 12.0.0 for unencrypted keys.

Answered: How can I encrypt existing files?

Thu, 07 Aug 2025 07:04:03 +0000

There is a way to encrypt (and decrypt) existing files via the SSH command-line. See the encrypt command in the command list here.

If you obtain a file listing of files to encrypt, you could generate a script to be run to encrypt each file as described here. Your script would consist of a series of commands like this:

encrypt -s /home/myuser/test_plain.txt -d /home/myuser/test_encrypted.txt

Note that it uses paths from the virtual file system, not Windows.

We recommend trying out a single file to start with and check that it is working as expected before you encrypt the entire file system. And consider backing up your files first!

Answered: How do I know if my cipher is supported?

Tue, 08 Jul 2025 14:58:06 +0000

The issue most likely is that the server is using a custom diffie-helman group that isn't accepted by the client.

Try disabling DHE ciphers and use ECDHE ciphers instead.

Answered: Listing only subfolders and a user has permission for

Tue, 24 Jun 2025 06:16:25 +0000

Yes — in CompleteFTP Enterprise MFT, you can create a JavaScript (JSS) file-system extension that filters directory listings so only content that the current OS user (Windows or Linux) has permission to access is shown. This allows you to dynamically hide any entries the user lacks access to.

How to set it up:

In CompleteFTP Manager, go to the Extensions panel.
Click Add extension > JavaScript (JSS) extension > File System.
Name the extension something like Filtered Folder.
Paste the following code into the script editor:

function getBaseType() {
    return "windows";
}

function getFileInfos(path, pattern, session, node) {
    return base.getFileInfos().filter(f =>
        !f.isFolder || hasListPermission(system.getFile(`${node.path}/${path}/${f.name}`))
    );
}

function hasListPermission(folder) {
    try {
        // Attempt to enumerate contents — succeeds only if user has ListFolder permission
        System.IO.Directory.EnumerateFileSystemEntries(folder.adapterAbsolutePath).GetEnumerator().Dispose();
        return true;
    }
    catch (e) {
        return false;
    }
}

Behavior summary:

Works for any subfolder at any depth beneath the mounted folder.
Automatically respects inherited ACLs, deny rules, and other OS-level permissions.
Filters both files and directories, only showing items that the current user has permission to list.
Works for OS users — i.e., authenticated users mapped to Windows or Linux accounts via CompleteFTP.
No special handling of ACLs is required — access is tested directly by attempting a listing.

This approach is ideal if you want to emulate ABE-style visibility without manually managing permissions in your application layer. Let us know if you'd like a version that includes logging for easier debugging or auditing.

The host signature is invalid or the host key was not accepted!

Fri, 13 Jun 2025 01:34:04 +0000

I am using edtFTPj/PRO v8.2.2 and am getting this exception:

com.enterprisedt.net.ftp.ssh.SSHFTPKeyException: The host signature is invalid or the host key was not accepted!

at com.enterprisedt.net.ftp.ssh.SCPClient.connectSSH(SCPClient.java:1181)

…

Caused by: com.enterprisedt.net.j2ssh.transport.kex.KeyExchangeException: The host signature is invalid or the host key was not accepted!

at com.enterprisedt.net.j2ssh.transport.TransportProtocolClient.performKeyExchange(TransportProtocolClient.java:461)

…

I have this simple Java test client:

import java.io.IOException;

import com.enterprisedt.net.ftp.FTPException;

import com.enterprisedt.net.ftp.Protocol;

import com.enterprisedt.net.ftp.SecureFileTransferClient;

public class FTPClient {

public static void main(String[] args) throws FTPException, IOException {

SecureFileTransferClient client = new SecureFileTransferClient();

client.setRemoteHost("ftptest.xxx.com");

client.setRemotePort(22);

client.setUserName("user");

client.setPassword("password");

client.setProtocol(Protocol.SFTP);

client.setServerValidationEnabled(true);

client.connect();

client.uploadFile("/tmp/local.txt", "remote.txt");

client.disconnect();

}

Debug logging seems to indicate a key exchange problem:

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.590 : Starting key exchange

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.590 : Determine Algorithm

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.591 : Client Algorithms: [ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group-exchange-sha1, diffie-hellman-group-exchange-sha256, ext-info-c]

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.591 : Server Algorithms: [diffie-hellman-group14-sha1, curve25519-sha256, curve25519-sha256@libssh.org, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group1-sha1]

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.591 : Returning ecdh-sha2-nistp256

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.591 : Key exchange algorithm: ecdh-sha2-nistp256

INFO [ECDHSha2] 12 Jun 2025 15:04:48.591 : Starting client side key exchange.

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.645 : Sending SSH_MSG_KEX_ECDH_INIT

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.742 : Received unregistered message: SSH_MSG_KEX_ECDH_REPLY

DEBUG [ECDHSha2] 12 Jun 2025 15:04:48.746 : calculateExchangeHash()

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Verifying host ftp.inmoment.com,44.239.215.42

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Determine Algorithm

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Client Algorithms: [ssh-rsa, rsa-sha2-256, rsa-sha2-512, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, ssh-ed25519, ssh-dss]

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Server Algorithms: [rsa-sha2-512, rsa-sha2-256, ssh-rsa, ssh-rsa]

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Returning ssh-rsa

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.749 : Selected algorithm ssh-rsa

DEBUG [SshRsaPublicKey] 12 Jun 2025 15:04:48.753 : Signature length=404

DEBUG [SshRsaPublicKey] 12 Jun 2025 15:04:48.755 : Verifying signature (com.enterprisedt.cryptix.provider.rsa.SHA1_RSA_PKCS1Signature)

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.757 : The host signature is invalid

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.757 : sendDisconnect(9,'The host signature is invalid or the host key was not accepted!')

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.757 : Sending SSH_MSG_DISCONNECT

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.757 : stop() called

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.758 : Disconnect: The host signature is invalid or the host key was not accepted!

DEBUG [State] 12 Jun 2025 15:04:48.758 : Updated state to 5

DEBUG [TransportProtocolCommon] 12 Jun 2025 15:04:48.758 : sendDisconnect(11,'The host signature is invalid or the host key was not accepted!')

Any thoughts?

Answered: Modify 'From' email address and subject

Fri, 06 Jun 2025 08:18:51 +0000

Your sample code shows the from email address (sender@test.com) and the subject (Files uploaded).

For more details see JSS API guide in our User Guide, here.

Answered: Is x509v3-ecdsa-sha2-nistp256 supported with latest edtftp-pro version 8.2.1

Thu, 05 Jun 2025 06:53:18 +0000

No, we currently don't support using X.509 certificates for SSH.

Answered: When will EDF FTP.NET Support Session resumption for TLS1.3

Mon, 19 May 2025 08:57:24 +0000

TLS 1.3 resumption is now supported in edtFTPnet/PRO 12.7.0.

Answered: How I find out what ciphers are supported for an edtFTPj/PRO version?

Fri, 09 May 2025 10:43:27 +0000

The list of TLS/SSL ciphers for FTPS protocol in our edtFTPj/PRO product can be viewed in the User Guide here. Please note that the User Guide online might not be the very latest release, so please check the API documentation included with the product download.

Answered: Can users update their own email address?

Wed, 30 Apr 2025 01:33:08 +0000

Currently, a non-admin user can't do this. It's a good idea though.

Answered: Preventing multiple sessions per user (HTTP FileManager)

Mon, 28 Apr 2025 03:38:56 +0000

Currently, this isn't possible. What do you need this for?

Answered: What versions of SFTP and TLS are supported by edtFTPj/PRO 5.2.3?

Mon, 28 Apr 2025 03:37:17 +0000

Yes, edtFTPj/PRO version 5.2.3 supports TLS 1.2 and SFTP version 3

Answered: Sending email in HTML format

Fri, 28 Mar 2025 22:49:59 +0000

Currently, this isn't possible. I've added a feature request for this.

Answered: massively change the permissions of all folders

Fri, 21 Mar 2025 01:23:23 +0000

You can do bulk permissions updates directly to the CompleteFTP config database as follows:

Close CompleteFTP Manager if it’s running
Stop the CompleteFTP service
Back up your existing configuration by copying the file at the following path to another directory
C:\ProgramData\Enterprise Distributed Technologies\Complete FTP\config.sdf
Open a Windows command prompt as Administrator
Execute the following command:
"C:\Program Files\Complete FTP\Server\cftpconfig.exe" /q "UPDATE [Node] SET [Permissions] = '750' WHERE GroupID = '8a9b1ba4-5d1b-41f6-893a-f99a319be033'"
The permissions are Unix style, so 750 in this example means full-control by owner, read-only by group and none for anyone else. The where clause restricts the changes to the users group.
Start the CompleteFTP service
Open CompleteFTP Manager and check if the paths changed as you expected.
If the changes are not as you expected then restore the config.sdf file that you backed up in step 3 and try again.

Answered: Is TLS session resumption supported?

Tue, 04 Mar 2025 02:54:52 +0000

CompleteFTP currently supports TLS session resumption up to TLS 1.2.

TLS 1.3 has a very different kind of session resumption based on session tickets, and currently this isn't supported.

We do intend to add support for this soon.

Answered: insufficient_security(71) in all connection Library v. 12.2.2.0

Mon, 17 Feb 2025 21:18:10 +0000

First thing to try is to disable TLS_DHE_RSA_* ciphers.

Answered: Does EnterpriseDT have a Maven repo we can download the jars from?

Wed, 12 Feb 2025 18:49:11 +0000

No, we don't have a Maven repository.

Answered: On edtFTPnet 11.1.1 all transfers are timing out, it only works if the cert is installed locally on the client.

Tue, 11 Feb 2025 03:19:17 +0000

In the first instance, when an issue is encountered, please upgrade to the latest version of edtFTPnet/PRO.

Answered: CompleteFTP - Get New Users

Mon, 10 Feb 2025 10:50:17 +0000

If you have a current support agreement please open a support ticket here. Please also explain what you mean by "last Day" as it is unclear what you require?

Answered: What could cause "Expected exception : The socket is EOF" that suddenly started appearing.

Sat, 08 Feb 2025 04:08:02 +0000

It's not obvious what the issue is from your error log. In the first instance, it's always best to be running the latest version of edtFTPj/PRO. Have you upgraded to the latest?

Answered: handshake_failure(40) exception when connecting with Version 12.1.1.0

Tue, 07 Jan 2025 05:17:43 +0000

The most likely causes of this error are:

The server and client do not have any common cipher suites enabled
The server does not support the TLS version
The server certificate is self signed or does not match the hostname
Firewall blocking connection. The error: "ERROR [SocketController] : FTPConnection.6461 OnReceive - caught exception - closing" is very often a firewall intervening and blocking the connection

Solution:
Check with the server admin whether they support your version of TLS, and that both the client and server have at least one compatible cipher. Check the server certtificate is valid. You can also check whether the server allows you as the user to use the FTPS protocol?

If you still experience difficulties you will need to open a support ticket here - please make sure that your support agreement is up to date and valid.

Answered: Can I send email notifications to all members of a group?

Mon, 02 Dec 2024 20:40:26 +0000

Instead of adding an Email Notification, you can add a Process Trigger that uses the JSS API to find the members of a group and send emails to them.

To add it, please follow these instructions:

Open CompleteFTP Manager
Select the Events panel
Verify that the Process Trigger tab is selected
Click Add
Enter a Name for your process trigger
Choose the Events that you want to notify people about
Enter the Folder filter, User filter and Site filter as required. Note that the user filter specified the users for which the process trigger is triggered, not the recipients of the emails.
Select JSS Script as the Type
Copy the script below into the Script field.
At the bottom of the window, next to Grant permissions of, select admin (since your script requires access to the CompleteFTP configuration).
Change the values of emailGroup, fromEmail, subject, messageTemplate as desired. Note that the text in curly brackets, like {fullName} are properties of the User object, as described here.
In the Users panel, add all users who you want to email to the group you’ve named as the emailGroup in your script.
Ensure that all the users in that group have email addresses (and Full name, if you’re using that property in your message).
Click Apply changes
Test it.

const emailGroup = "users";
const fromEmail = "hcaandersen@fastmail.com";
const subject = "Hello";
const messageTemplate = `Hi {fullName},

This is a message from CompleteFTP.

Your email: {email}

Regards,
CompleteFTP
`;

// -------------------------------------------------------------------

let config = system.getConfig();
let group = config.groups.get(emailGroup);
if (!group) {
    console.error(`Unknown group, ${emailGroup}`);
    return;
}
console.log(`Emailing members of group, ${emailGroup}`);
let members = group.members.toArray();
members.forEach(userName => {
    let user = config.users.get(userName);
    if (!user.email) {
        console.warn(`User ${userName} has no email address set`);
        return;
    }
        
    console.log(`Emailing ${userName} at ${user.email}`);
    const personalizedMessage = renderTemplate(messageTemplate, user);
    mail.send(user.email, fromEmail, subject, personalizedMessage);
});

function renderTemplate(template, variables) {
    return template.replace(/{(\w+)}/g, (match, key) => {
    return key in variables ? (variables[key]??"") : match;
    });
}

Answered: How do I see the last login time of a user in CompleteFTP?

Wed, 06 Nov 2024 19:52:14 +0000

If you're using Professional Edition or better you can see last logins in the ‘Last login by user’ report as shown below:

Answered: How do I use a JSS custom command to add a Windows user?

Tue, 05 Nov 2024 19:50:09 +0000

Adding the Custom Command:

1. Open CompleteFTP Manager
2. Select Extensions
3. Click Add extension -> Javascript (JSS) extension -> Command Commands
4. Enter CustomAdmin (or some other name) in the Name field
5. Copy the following script into the script editor:

function CreateWindowsUser(userName, virtualFolderPath, windowsMappingPath) {
    // Step 1: Get the system configuration
    var config = system.getConfig();

    // Step 2: Check arguments
    if (config.users.get(userName))
        throw 'Error: User already exists';
    if (config.folders.get(virtualFolderPath))
        throw 'Error: Folder already exists';
    
    // Step 3: Create a new non-Windows user
    var newUser = config.users.add('Windows');
    
    // Step 4: Assign username
    newUser.userName = userName;

    // Step 5: Add a Windows folder with a mapping path
    var folderType = "WindowsFolder";
    var windowsFolder = config.folders.add(virtualFolderPath, folderType, windowsMappingPath);

    // Step 6: Assign the Windows folder as the home folder for the user
    newUser.siteMapping[0].homeFolder = windowsFolder.fullPath;

    // Step 7: Set permissions for the Windows folder (optional)
    windowsFolder.access.owner.userName = newUser.userName;
    windowsFolder.access.owner.permissions = ["All"];
    windowsFolder.access.group.groupName = "users";
    windowsFolder.access.group.permissions = [];
    windowsFolder.access.allUsers.permissions = [];
    windowsFolder.access.inherits = false;

    // Step 8: Apply changes to the configuration
    config.applyChanges();
    
    return `Windows user ${userName} added successfully`;
}

6. Select the Permissions tab
7. Add a group permission for the admins group to access the CustomAdmin extension.
8. Select the Sites tab
9. Select the Admin site (won’t be visible unless Options -> Show system users/folders/sites is checked)
10. Enable SSH terminal access
11. Apply changes

Invoking the command:

Essentially you just log into via SSH to port 14983 and execute a command like the following:

CreateWindowsUser theusername /the/home/folder/in/CompleteFTP C:\the\windows\directory

There are many ways to do this. Since Windows includes OpenSSH, you can execute the following command:

ssh admin@localhost -p 14983 "CreateWindowsUser theusername /the/home/folder/in/CompleteFTP C:\the\windows\directory"

You can also set up public key authentication for the admin user if you like, so that you don’t have to enter the password every time. You can also add a new admin user and user that if you’d like to separate this from standard admin.

Answered: Incomplete Download from Win2012

Tue, 29 Oct 2024 09:20:47 +0000

We will probably need a debug log which you can attach to a ticket by going to our support portal here.

Answered: Receive "Global request keepalive@jcraft.com not supported" message

Mon, 28 Oct 2024 18:01:01 +0000

The client is sending a custom keep-alive message to try to keep the connection to the server open. It can be safely ignored, and it's not indicative of any server load problem at that frequency. However, if it's your own client, you can probably disable this behavior.

Answered: how to resolve the issue The negotiation of encryption algorithm has failed. This is we are getting the edtFTPnetPRO dll

Tue, 08 Oct 2024 11:51:37 +0000

Hi,

Please open up a support ticket at our support portal here if you have a current support agreement. This can only really be troubleshooted with a debug log showing the connection.

Answered: Is there the possibility to throttle the FTP data transfer speed?

Sun, 29 Sep 2024 07:43:00 +0000

Thanks for the reply!

It was actually the FXP_READ issue again where only 1 Max Queued Request can be handled.

Setting it to 1 with SSHFTPClient.setMaxQueuedReadRequests() did the trick for this customer we interface with!

Very cool, but, good to know that speed also can be throttled and not a good idea to pursue and getting to the bottom of the underlying problem is best.

Thanks!

Jan

Answered: Unable to save changes after updating the software.

Wed, 11 Sep 2024 11:58:56 +0000

Please open up a support ticket here under "Technical Support".

Answered: Whether CVE-2023-22551 is reported in edtftpj-pro jar

Mon, 09 Sep 2024 03:48:29 +0000

This CVE is for some random FTP project on GitHub. It has no relation to edtFTPj/PRO.

Answered: Encryption At Rest

Fri, 09 Aug 2024 06:00:27 +0000

Our main concern with AES-256 is that AES-256 is typically about 20% to 40% slower than AES-128. That’s why we chose to go with AES-128. Of course, as machines get faster this is less of a concern, so we do intend moving to AES-256 in a future release