When attempting to set up use a new SFTP connection we are receiving the following error:

SFTP error 11
Connection lost (error code is 10058)

Our existing SFTP connection is working properly. We are just seeing this with any new connection we are trying to create.

Are you able to connect with the SFTP Explorer? Could you attach a screenshot of the log there if it fails?

---

I am getting the error when attempting to connect through the Explorer. I don't see anything in the transfer log or terminal log at the bottom of the window.

The only things I am seeing in the window are the time and events. It lists a serverkey being received and the following 2 events are the errors I described previously.

Please try experimenting with compression on/off and different SSH methods.

---

I tried with both SSH options selected with and without compression and tried with and without compression selecting one SSH option at a time. I also tried with both de-selected with compression on and off.

I received the same error in each of the instances.

We will research some more and then get back to you.

---

Could you give us the name and version of the SSH server on that machine. That would help us.

---

Hi,
I am seeing a similar issue but getting error 10060 - Connection timed out.
I am able to sftp in with no issues from the command line outside of VC.
the version of the stfp is "SFTP protocol version 3".

We need the name of the SSH server and version in order to investigate more.

---

the SSH server is fts.jpmchase.com and we use the default port.
I don't know the answer to the version question - the only other hint is that when I try to open the sftp through Firefox I have to enter the following: ftp://fts.jpmchase.com/  and not just the server name.

the SSH server is fts.jpmchase.com and we use the default port.
I don't know the answer to the version question - the only other hint is that when I try to open the sftp through Firefox I have to enter the following: ftp://fts.jpmchase.com/  and not just the server name.

Hmmm.. you are referencing to a FTP server but you said you had an SFTP error. Those are two different protocols. You have probably selected SFTP instead of FTP/FTPS in the Connection dialog of VisualCron. That is why you get an error.

---

you are right! my bad - it is ftps and now everything works.

by the way - we have about 100 jobs running in production already - and we are very impressed with the software and the power of it. thanks much for great support as well!

you are right! my bad - it is ftps and now everything works.

by the way - we have about 100 jobs running in production already - and we are very impressed with the software and the power of it. thanks much for great support as well!

Thanks for the feedback!

---

Dear Henrik:

Hi. We had another problem with FTPS. We have a job that runs every ten minutes that makes an FTPS connection to a server and downloads a file. It would always fail when triggered from the timer, but when you trigger it manually by clicking "run task," it always worked.

We found that if we change the trigger to run not on the 0th second but on some other second, like the 27th, then it would work when triggered from the timer. We think this is because it's colliding with some other job that also runs on the 0th second. Is this possible?

So we have this working now, but it would be nice to not have to worry about tasks colliding.

Dear Henrik:

Hi. We had another problem with FTPS. We have a job that runs every ten minutes that makes an FTPS connection to a server and downloads a file. It would always fail when triggered from the timer, but when you trigger it manually by clicking "run task," it always worked.

We found that if we change the trigger to run not on the 0th second but on some other second, like the 27th, then it would work when triggered from the timer. We think this is because it's colliding with some other job that also runs on the 0th second. Is this possible?

So we have this working now, but it would be nice to not have to worry about tasks colliding.

Which version are you running now? Please upgrade to 6.0.3 if using older.

---