KB Article #181805
Stalled or Aborted SCP downloads when using Repository Encryption
Problem
When using Repository Encryption in ST, you may obseve errors with SCP client downloads - transfers are getting 'stalled' and the Server Log and File Tracking log messages of the types - Transfer aborted and/or Write to remote failed. The issues are observed only with accounts which have Repository Encryption enabled.
Interestingly, the issue is not present with SFTP, however, you will notice that files downloaded over SFTP do not report 100% completion, but would rather report a lower percentage (like 85%).
Resolution
When Repository Encryption is enabled, SecureTransport (by default) reports the encrypted size of the files to the SSH (SCP) client's list request. SCP uses the size from the ST's list response to compare it with the size of the downloaded file (this is a built-in integrity check), and since the sizes do not match, the SCP client gets confused and unable to download the files.
To resolve the issue, you must set the Stfs.Encryption.ListDecryptedSize Server Configuration parameter to true on all Backend and Edge servers in the environment so that SecureTransport starts reporting the actual file size instead of the encrypted size. The configuration change requires a restart of all ST services.