I have added a new SFTP connection to an external partner (port 22, username/password authentication, in VisualCron 9.3.5 and now also in 9.4.0), and when I then go into "Connection Explorer" I can connect to the server and browse the server, download files, etc. without problems, as expected.

But if I use the same connection in a task, it will time out - and if I open "Manage Connections", open the new connection and click the "Test" button , it also times out ("Connection test failed. Error: Connection timeout").

What could cause the connection to time out when testing or using it in a task, while it works as expected when opened through the "Connection Explorer"?

Thanks in advance!

Hi,

Check your SSH key setting. It falls out when updating.

S

Hi Svein - thanks, but I don't think that is the problem. I can connect through the Connection Explorer without problems, but Test always times out.

BR

Hi Svein - thanks, but I don't think that is the problem. I can connect through the Connection Explorer without problems, but Test always times out.

BR

Hi,

That sounds odd. We haven't heard of a case like that before. Would it be possible for us to get a test account to that partiular SFTP? If so, please send it to support@visualcron.com

---

Hi Michael,

Thanks, I have sent an email as requested.

Best regards,
Michael

Hi I have the exact same issue,

the SFTP connection runs fine in Connection Explorer; I can browse the files and download them but when used in a task it ends with Connection error 10060. I've tried many cerdentials and also with no credentials for good measure but result remains the same.

I cannot send a test user as this is hosted by another business and contains propriatery trade data.

Anything I can try?

Thanks in advance

@  mkrag

In my case, it ended up being a firewall issue. Our VisualCron server is located at a different site to the client.

From what I can tell, the VisualCron Client was connecting to the SFTP server through Firewall 1. When the job was being run on the server, it would try connecting through Firewall 2, which was blocking the traffic.

Hope this helps
Brad

Thank you,

never entered my mind that could be it because ran in explorer and not in task. It turns out that when the explore is used the firewall sees the local machine and lets through but when the task runs it sees the source as visualcron server which doesnt have a rule for that particular port # and blocks...

Thanks !

Thank you,

never entered my mind that could be it because ran in explorer and not in task. It turns out that when the explore is used the firewall sees the local machine and lets through but when the task runs it sees the source as visualcron server which doesnt have a rule for that particular port # and blocks...

Thanks !

Great! Glad you got it solved.