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.
Discussion posts and replies are publicly visible
Do you run WinSCP or FileZilla on the exact same machine as the Appian installation runs on? I assume this is not the case. Did you check for any firewall or other IP filters anywhere on the way from Appian to that FTP server?
Good afternoon Estefan,
As you say, I have done the tests with WinSCP and FileZilla from my PC. The Appian environment we are using is in the cloud.And FTP is open to the internet, so anyone with connection data can access it.
I don't know if you can think of anything else.
Thank you!
Did you check the tomcat-stdout log file for additional details?
Only the error that I attached in the description appears.
What exactly is the communication protocol? There is SFTP and FTPS, and it is not the same.
Hi Stefan,The protocol is FTPS, sorry if the value of the key may be confusing, we will change it to make it more obvious.
Greetings and thank you!
I am not asking because of any naming concerns, but it might be that the server only support one variant, while the plugin does the other.
Hi Stefan,
We connect to the server with filezilla with this protocol and the smart service we are using FTPS.I don't know if that's what you mean.
Thanks in advance
Stefan is trying to point out that this plug-in is intended for use with sFTP protocol. Like him, I'm not clear whether it would work with other variations like FTP or FTPS. The server I've used it with successfully is just sFTP.
Hi Mike,
If I'm not understanding wrong, the plugin supports all protocols:
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.
I might be wrong about this protocol stuff, but I had a quick look at the source code and it seems like the plugin contains implementations for each one and somehow needs to know which one to use.
Thinking further, typically, we use a syntax like ftp://server.test or sftp://server.test to define which protocol to use. Then, I assume that the plugin picks the correct code.
Well, I had just set up a server to do this test and it connects correctly, the only difference I see (without being able to go into the details of my company's server because I would have to see it with the IT department) is that in mine for testing input I send port 21 and in the real one I must send 21021.
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.
I will do so, I will comment on the answer when they give me a solution.
Thank you so much!