FTPS Smart service fails when retrieving directory information

Question

Good morning, 
 We are trying to recover directory information with the Get Remote Folder Contents smart service (FTPS). 
 The configuration we have is: 
 fileTransferConf: 
 'type!{plugins.ps.appiancorp.com/.../}FT_Config'( 
 serverHostName: " ftp.prueba.es ", 
 serverPort: 21021, 
 scsExternalSystemKey: " sftp_prueba_appian ", 
 usePerUserCredentials: false() 
 } 
 Server File Path: "/DEV/" 
 * In the user console we have configured the scsExternalSystemKey with the corresponding user and pass. 
 
 The error obtained is: 
 ERROR com.appiancorp.ps.plugins.filetransfer.ftps.GetRemoteFolderContentsOverFTPS - org.apache.commons.net.ftp.FTPConnectionClosedException: Connection closed without indication. 
 
 The credentials are the same ones we are using in WinSCP and FileZilla. Both work fine to connect to FTPS site. We have tried adding documents so that the route is like this: 
 "/DEV/test.docx" 
 Has anyone faced the same problem? 
 
 A greeting and thanks in advance.

Mike Schmitt · Answer

sandrap5933 said: In the user console we have configured the scsExternalSystemKey with the corresponding user and pass. 
 Can you confirm that the "key" listed in the third-party credential store is *exactly* "ftp_appian"? This property is not editable (afaik) after it's been initially configured. 
 Is "prueba.es" the FULL host name? As in, you're sure it's not "sftp.prueba.es", or some other permutation along those lines? 
 Have you tried passing the path as just "/" for starters?

Mike Schmitt · Answer

ok, thanks for confirming. As i mentioned, I just hadn't personally tested it on a protocol outside of standard sFTP. 
 Are you able to make a connection between your system and a public ftp / sftp testing site, just for troubleshooting? When I was first building my appian-based sFTP solution, I found it helpful to connect to one of these just for an example of a remote directory read (i was able to find established and reputable read-only servers with public credentials for testers to use, just by googling). If one of those works but the one you're trying still fails, then you might have an internal networking / firewalling issue with your particular server, which you'd need to resolve with your internal IT folks.

Mike Schmitt · Answer

sandrap5933 said: in mine for testing input I send port 21 and in the real one I must send 21021. 
 Check with your IT folks to see whether your special port might be getting blocked. As it's not a standard port for incoming connections (afaik), it also just might be an issue of it not automatically have port forwarding turned on at whatever server it's hosted at, meanining no connection from outside at that port would automatically find your FTP server until it's configured properly for that purpose.

FTPS Smart service fails when retrieving directory information

Top Replies