If you find yourself presented with task failing because they cannot access MOVEit Transfer, This could be due to a number of reasons. To allow your tasks to continue running while you diagnose the issue, We can put in a small workaround to allow connections to continue over SHH. 

Background:

When you create a MOVEit Transfer host in MOVEit Automation it will create a host based on HTTPS protocol over port 443. This is the default setup when you create this connection.  If the nature of the issue is the Https listen on your MOVEit Transfer server, You may see a number of tasks fail that will give a similar error in the task logs. 

If we look at the example below we can see that the “HttpSendRequest” failed to connect to the server as Automation was unable access the URL. This can happen when a listener is rejecting traffic on that specific port. 

Workaround:

What we can do as a workaround is to setup a new SSH (SFTP) host to the same MOVEit Transfer. MOVEit Transfer at its core is an SFTP server which will allow connections over port 22. This way Automation can continue to connect and complete the tasks as required. 

You can use all the same credentials and configuration as your exsisting MOVEit Transfer host except when creating a new SSH host please select SSH Host as shown on the left. Once complete all you will need to do is going to the failing task and amend the step that is using the MOVEit Transfer Host (Upload or Download) to the new SSH host that you have created. 

We would advise that you clone the task and make amendments to the cloned task. Once cloned and updated you can turn off the scheduling for the original task and enable the schedule on the clone until the root cause of the issue has been resolved. 

This will allow you to continue tasks while you can investigate into the root cause of the connection issue between MOVEit Automation & MOVEit Transfer.