Potential defect in cloud storage location mapping

Overview

In SFTP Gateway v3.7.1, there is a bug where the Resolved Cloud Path may not reflect where the SFTP user actually points. For example, an SFTP user mapped to Location B could actually point to Location A.

This bug only affects some SFTP users and can only happen in certain conditions.

If you are affected by this issue and would like support, email us at support@thorntech.com.

Is my version affected?

This bug only affects SFTP Gateway v3.7.1, which was released on March 27, 2025.

To see your version of SFTP Gateway, log into the web admin portal and scroll to the bottom. The version will show up in the footer.

Footer

Or, you can SSH into the VM, and cd to this location:

/opt/sftpgw/

You will see a jar file with the version number.

If you see multiple jar files, run this command:

ps -ef | grep java

This will show you which jar is currently being used.

Does this issue apply to me?

This bug only affects some SFTP users and can only happen in certain conditions.

First of all, this issue applies only if you are mapping to multiple Cloud Connections. For example, each SFTP user points to a different Cloud Connection.

This issue typically affects the most recent Cloud Connection that you mapped to. For example, if you mapped the home directory of /users/robtest/ to a Cloud Connection, SFTP in as robtest to verify if you are actually connecting to the correct location.

This bug is caching related, so you may not encounter any issues. This is because any folder modification or permission change will clear the cache.

Short-term workaround

If the above conditions apply to you, you should clear the cloud mount cache. This is to ensure that every SFTP user is pointing to their expected location.

Note: This is a temporary workaround until you are able to update to v3.7.2 or later.

You can use any ONE of the following ways to clear the cache:

Create a test SFTP user with default home folder settings. This will trigger the creation of a new home folder.
On the Folders tab, create a new folder. It doesn't matter what you create, or where you create it.
On the Folders tab, change the permissions on any folder. For example, change it from read-write to read-only, and then back to read-write.

Upgrading to the next version

We highly encourage users to upgrade to version v3.7.2.

For Single instances, we recommend launching a new instance of v3.7.2 to get the latest OS security patches, and then importing a backup of the v3.7.1 SFTP Gateway setup.

For HA stacks, we recommend a scale up / scale down procedure to migrate to v3.7.2 without any downtime.

SFTP Gateway Support

3.0