4

I have a Logic App that triggers when a Blob is added or modified. The next action is to Copy file to FTP. This only works when we edit the FTP connection and delete the port. When this runs manually it works fine.

enter image description here

After a few minutes, the API Connection seems to revert back to port 21. When this happens, the Logic App fails on the FTP action with a "BadGateway" error. enter image description here

The error message is:

An FTP protocol violation was detected. This could be caused by an implicit TLS/SSL configuration of the FTP server that is not supported. Please try explicit TLS/SSL.

When I go back to review the FTP API Connection, the Port is set to 21. Clearing it and rerunning the Logic App succeeds. I have tried port 990 explicitly but that also gives a BadGateway.

enter image description here

Why would the Azure Logic App reset to port 21 and what can I do permanently fix this?

shanabus
  • 12,989
  • 6
  • 52
  • 78
  • have you tried to delete the api conenction and recreate one ? also port 20 and 21 are dfault port for ftp – Thomas May 01 '18 at 21:38
  • Thanks @Thomas I have deleted and created a new one, same thing. It works momentarily then resets something behind the scenes that breaks it. I will try port 20. – shanabus May 02 '18 at 14:27
  • @Thomas port 20 for our FTP server must be blocked or not configured, this produced at differenge (504) GatewayTimeout – shanabus May 02 '18 at 14:41

0 Answers0