SFTP connection error 114 and error 10058 - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

Dgaliffa Unknown
Free support Topic Starter

2023-04-14T13:08:39Z

Hello,

We have a bunch of SFTP jobs/tasks built and functioning on our VisualCron server. We just tried to build a new one, using a public/private key, and we keep getting a SFTP error 114 and 10058. We tested this same connection info in Filezilla and it connects fine. We seen a lot of forum posts with other users having these same errors and tried things like disabling the auto authentication (pw auth, keyboard auth), tried enabling and disabling different versions of SFTP in extra settings. I'm not really sure where to go with this, so I was hoping you can take a look at the event log and then see if you spot anything or have any new suggestions.

The SFTP is a 3rd party site but they already have our public key and we can connect fine using Filezilla. Any thoughts on what this issue can be?

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Dgaliffa Unknown
Free support Topic Starter

2023-04-14T13:10:39Z

https://imgur.com/a/PAw77uo

Edited by user 2023-04-14T13:11:18Z | Reason: Not specified

milian foster
Free support

2023-04-26T09:25:56Z

Hello,
I would like to suggest you
Error code 114 in SFTP usually indicates a connection timeout while error code 10058 indicates that the connection was reset. These errors can occur due to various reasons, such as network issues, firewall restrictions, incorrect configuration settings, or server-side issues.

Since you have already tested the connection using Filezilla, it is likely that the issue is related to the configuration settings in VisualCron. Here are a few things you can try:

Double-check the connection settings: Make sure that you have entered the correct SFTP server address, port number, and login credentials in VisualCron. Also, check if the remote directory path is correct.

Check if the private key is correctly configured: Make sure that you have configured the private key file correctly in VisualCron. You can also try using a different private key file to see if that resolves the issue.

Verify if the firewall is blocking the connection: Make sure that the firewall on your VisualCron server is not blocking the SFTP connection. You can try temporarily disabling the firewall to see if that resolves the issue.

Check if VisualCron is using the correct SFTP protocol version: Make sure that VisualCron is using the correct SFTP protocol version that is supported by the SFTP server. You can try changing the SFTP protocol version in the VisualCron settings to see if that resolves the issue.

Check if there are any server-side issues: Contact the SFTP server administrator to see if there are any server-side issues that may be causing the connection errors.

If none of the above solutions work, you can also try enabling debugging in VisualCron and checking the event log for more detailed error messages. This may provide more insights into the root cause of the issue.

I hope this helps!

Danny van Oijen
Paid support

2023-05-10T09:46:39Z

We also have these issues, this started with version 10.0.1
Tasks using this connection shows: Object reference not set to an instance of an object.

The connection Explorer shows:

SBSocketClient.EElSocketClientConnectionLostError: Connection lost due to error 10054
   bij SBSocketClient.TElBaseSocketClient.ReportConnectionLoss(Int32 ResultCode, Int32 SupplErrorCode)
   bij SBSocketClient.TElBaseSocketClient.DoReceive(Object Sender, Byte[]& Buffer, Int32 MaxSize, Int32& Written)
   bij SBSSHCommon.TElSSHClass.DoReceive(Byte[]& Buffer, Int32 MaxSize, Int32& Written)
   bij SBSSHClient.TElSSHClient.DataAvailable()
   bij SBSocketClient.TElBaseSocketClient.DataAvailable()
   bij SBSocketClient.TElBaseSocketClient.DoMessageLoop(Boolean NoPeek)
   bij SBSimpleSftp.TElSimpleSFTPClient.Open()
   bij PEBCBBBENBMEPPPAHKHPCCOHPCCFBHBLGGHF.OCHLGMNAHFPMFFMCCEGDNFOLGPFBABHFGOFM(Object , PEBCBBBENBMEPPPAHKHPCCOHPCCFBHBLGGHF )
   bij ctlRemoteBrowser.ConnectThread(Object connectionObject) in C:\git\code\VisualCron\Connections\ConnectionExplorer\ctlRemoteBrowser.vb:regel 1619

Extended debug show:

10-5-2023 11:13:26        Err          Unhandled exception in  ProcessTaskFTP.Run: System.NullReferenceException: Object reference not set to an instance of an object.
   at (Object )
   at ConfigurationContainer.CalcRecord(Object , ConfigurationContainer )
   at VisualCronService.ConnectionHandlerClass.Connect(ConnectionClass cc, Boolean OpenConnection, VariableReplacerClass variableReplacer, Boolean bolDebugging, Boolean bolRaiseErrors, Boolean bolForceNewClient) in C:\git\code\VisualCronService\Jobs\ConnectionHandler\clsConnectionHandler.vb:line 421
   at VisualCronService.ConnectionHandlerClass.Connect(String strConnectionId, Boolean OpenConnection, VariableReplacerClass variableReplacer, Boolean bolDebugging, Boolean bolRaiseErrors, Boolean bolForceNewClient) in C:\git\code\VisualCronService\Jobs\ConnectionHandler\clsConnectionHandler.vb:line 172
   at VisualCronService.ProcessTaskFTPClass.Run() in C:\git\code\VisualCronService\Jobs\TaskProcesses\Net\FTP\clsProcessTaskFTP.vb:line 92

Vassilis Devletoglou
Paid support

2023-05-10T12:35:29Z

Hi guys, we have the exact same problem. It worked fine under 9.9 version but as soon as we updated we get the same error.

In addition, the connection explorer freezes as soon as we open it and we need to kill the client.

Originally Posted by: Dgaliffa Unknown

Hello,

We have a bunch of SFTP jobs/tasks built and functioning on our VisualCron server. We just tried to build a new one, using a public/private key, and we keep getting a SFTP error 114 and 10058. We tested this same connection info in Filezilla and it connects fine. We seen a lot of forum posts with other users having these same errors and tried things like disabling the auto authentication (pw auth, keyboard auth), tried enabling and disabling different versions of SFTP in extra settings. I'm not really sure where to go with this, so I was hoping you can take a look at the event log and then see if you spot anything or have any new suggestions.

The SFTP is a 3rd party site but they already have our public key and we can connect fine using Filezilla. Any thoughts on what this issue can be?

Danny van Oijen
Paid support

2023-05-10T12:44:35Z

If you updated to 10.0.1 re-download and re-install, it should be fixed. (here it works again)

Vassilis Devletoglou
Paid support

2023-05-10T16:49:24Z

Hi guys, i was able to find a working workaround. As I wrote before, on version 9.9 it was working and stopped as soon as i updated yesterday to the latest version.

Go to the Connection Settings, uncheck Auto adjust ciphers, Auto adjust exchange algorithms and Auto adjust MAC algorithms while keeping all items underneath it will work fine.

Also, please visual cron I have opened multiple tickets. If you go to Brute force test, on the left by default it says that it will use a proxy, and nothing works. If you uncheck it and you click test it will automatically check it back. You need to uncheck it again, stop and start to make it work.

This is over a year now.

Originally Posted by: Dgaliffa Unknown

Hello,

We have a bunch of SFTP jobs/tasks built and functioning on our VisualCron server. We just tried to build a new one, using a public/private key, and we keep getting a SFTP error 114 and 10058. We tested this same connection info in Filezilla and it connects fine. We seen a lot of forum posts with other users having these same errors and tried things like disabling the auto authentication (pw auth, keyboard auth), tried enabling and disabling different versions of SFTP in extra settings. I'm not really sure where to go with this, so I was hoping you can take a look at the event log and then see if you spot anything or have any new suggestions.

The SFTP is a 3rd party site but they already have our public key and we can connect fine using Filezilla. Any thoughts on what this issue can be?