Common Issues · SFTP Gateway Support

Overview

This article lists the most common support issues we've been seeing for SFTP Gateway on Azure.

Everything stops working after a reboot

After a reboot, SFTP users can no longer log in. Also, the web admin UI no longer comes up.

This can happen if the VM name includes uppercase letters, and the solution is to update the /etc/hosts file.

This issue has been fixed in version 2.001.04.

The web admin UI shows an error `Connection refused`

When running the web admin UI, you may see an error message:

localhost:636 Connection refused

This is usually a sign that the LDAP service is down. Here is an article for troubleshooting the LDAP service.

The web admin UI shows an error `nested exception`

After running a yum update, the web admin UI shows the error:

simple bind failed:
localhost:636; nested exception is javax.naming.CommunicationException: 

Root exception is javax.net.ssl.SSLHandshakeException:

To fix this issue, refer to this article, and run the command:

sudo /usr/local/bin/set-java-certs

How do I give one SFTP user access to another SFTP user

In some situations, you want one SFTP user (e.g. an internal user)to have access to one or more SFTP users (e.g. external vendors).

This feature is not built into SFTP Gateway, but there is a way to configure manually this using Linux commands.

Here is an article with instructions on how to set this up.

Thousands of files are stuck and the server is out of memory

By default, SFTP Gateway is optimized for getting files to show up in Blob storage quickly. This default configuration may not be ideal when uploading thousands of files.

Here's an article for configuring SFTP Gateway for more throughput.