Tools
The user cannot log in to the Serv-U SFTP via Gateway
This article describes a scenario where SFTP users cannot authenticate to Serv-U via Gateway
First published date
Last published date
Overview
- Can connect to the SFTP but is unable to authenticate
- Global level server activity showing it is attempting to connect but cannot authenticate
- SFTP client showing access denied even username or password is correct
- Login credentials works when testing it to connect directly to Serv-U MFT
- Serv-U hosting multiple domains with a single Gateway server or IP
Product section
Cause
- The Serv-U Gateway IP listener is configured on both domains listening on the same port 22
- When it happens, the connection usually goes to the primary domain in Serv-U (first created domain)
Resolution
- Make sure that each Domain is listening to a unique IP or ports
- If the Gateway has a single IP only and needs to configure to all domains hosted in Serv-U, you can define different port numbers (ex., SFTP port 22 can be port 2222 on other domains)
- Disable the Gateway listener on the domain that should not be listening to the SFTP