We have an FTPS connection using an HTTP proxy (Squid).

After upgrade from 9.4.0 to 9.9.6 the connection stopped working.

I tested the connection with the "Test" button in the connection properties, and after a while it returned "Success" so I thought i worked.

But when the relevant job ran it failed with: "Connection error 10035".


The VC host is not connected to the internet hence the proxy.

I could see the calls in the proxy log and I could connect with WinSCP from the same host as VC using the same details and proxy.


I could work around by removing the use of the proxy and creating a static route to a gateway connected to the internet - luckily the server also accepts that IP.


So: it looks like there is a bug in the proxy implementation of the current FTPS task. The control channel works (hits a non default port) - which is why the test succeded, I think. But the data channel ports are probably not set to use the proxy settings.

We have an FTPS connection using an HTTP proxy (Squid).

After upgrade from 9.4.0 to 9.9.6 the connection stopped working.

I tested the connection with the "Test" button in the connection properties, and after a while it returned "Success" so I thought i worked.

But when the relevant job ran it failed with: "Connection error 10035".


The VC host is not connected to the internet hence the proxy.

I could see the calls in the proxy log and I could connect with WinSCP from the same host as VC using the same details and proxy.


I could work around by removing the use of the proxy and creating a static route to a gateway connected to the internet - luckily the server also accepts that IP.


So: it looks like there is a bug in the proxy implementation of the current FTPS task. The control channel works (hits a non default port) - which is why the test succeded, I think. But the data channel ports are probably not set to use the proxy settings.

Could you please try and recreate the whole connection from scratch and see if it gives you the same issue?

Hi Michael

I have already removed/imported the involved certificate and created a new connection from scratch. But the issue is the same.

Without changing the connection settings (with proxy) it works when adding a static route to the host through an internet gateway - and stops working when removing the route.

To sum up:
1: I can observe the control channel connect in the proxy log.
2: The data channel only works with a route = bypassing the proxy.

Hi Michael

I have already removed/imported the involved certificate and created a new connection from scratch. But the issue is the same.

Without changing the connection settings (with proxy) it works when adding a static route to the host through an internet gateway - and stops working when removing the route.

To sum up:
1: I can observe the control channel connect in the proxy log.
2: The data channel only works with a route = bypassing the proxy.

Does it use IPv6 to connect when you do it via filezilla for example? Also, are you able to provide screenshots of proxy, and the connection information itself/test account? You can email it to support@visualcron.com