I'm getting an error while attempting to connect to an FTP site. The error is as follows:

Plugin returned errorcode 6. Error message=No further info.Will try again after ## seconds.

I've verified the host and connectivity settings via FileZilla. I am able to open a connection in FZ and upload and manipulate files so I'm certain that the host and username/password are correct.

I'm using FTPS(Implicit) on Port 990 to make the connection. I have tried it with across all of the supported protocols without success. I've tried it in passive mode and non-passive mode.

I've reached out to the vendor for assistance but have thus far gotten no where. I've got about a dozen FTP uploads configured in WatchDirectory and this is the first time I've had trouble with one using the app.

The history keeps showing messages:
FTP Library 3.5.3.731
FTP Library 3.5.3.731
Connected

Eventually I'll get the aforementioned error. Occasionally, I'll get:
Connection lost, will retry after ## seconds, message is 10060: The current connection has timeout.

I'd appreciate any insight that you guys could offer me on this. Thanks!

If the log says "connected", it (obviously) means the login succeeded.

For FTP and FTPS (not SFTP) connections, you should typically set the "Passive" option. Only on very rare occasions this should be "Active" (Passive NOT set). When the Passive option is set incorrectly you see the following behavior:
- you can connect
- when you use the "..." button next to "base directory" it can not properly show the window with the FTP directory listing. This is because the FTP server can not properly respond to the LIST command (to get the directory list on the FTP server).

Can you use the "..." button? Does it show a directory listing (without an error message)?

Perhaps the admin of this FTP server can see something in their logs.

Yep. We're using Passive mode. We've tested with and without, actually.

And no, the '...' button does not work. I get a timeout error. I've sent the server admin a list of the errors we're getting when we attempt to connect and asked him to check it against their logs of our connection attempts.