Solved: How to Fix Connection Issues when Executing Pipeline to FTP Server?

Troubleshooting Question

I’m encountering a connection problem while attempting to execute a Pipeline configured to FTP files to my own FTP Server. I followed the prescribed steps, including adding the IP range 20.195.68.0/24 to my FTP Server’s whitelist. However, the pipeline is still unable to establish a connection with the server.

In an effort to troubleshoot the issue, I set up a test FTP Server and directed the Pipeline to FTP files to this test server. When examining the server’s logs, I noticed incoming IPs that were not in line with the IP ranges mentioned in the reference article. These IPs include:

• 20.239.x.x
• 20.247.x.x
• 4.194.x.x

These IPs appear to be different from what was originally specified.

To ensure the successful functioning of my Pipeline for FTP operations to my target FTP Server, I’m seeking guidance on which IP range or domain I should include in the whitelist. It seems there might be variations from the expected IP ranges, and I want to ensure that the connection is established securely and reliably. Any advice on this matter would be greatly appreciated.

Solution: Alternative Approach for Addressing FTP Server Whitelisting

While the solution I’m suggesting may not directly resolve your current issue, I’d like to propose an alternative approach that can simplify your setup and improve security.

Whitelisting a large range of public IP addresses on your FTP server can be cumbersome and may not be the most secure option. Instead, consider deploying an Azure resource, such as a Virtual Machine (VM), and install the Azure DevOps agent on it. Here’s how it works:

Step 1: Azure VM Deployment: Set up an Azure Virtual Machine that you have full control over. This VM will act as a dedicated environment for your pipeline.

Step 2: Azure DevOps Agent: Install the Azure DevOps agent on the VM. This agent will allow you to run your pipeline on the VM.

Step 3: Static Public IP: Configure the Azure VM to use a static public IP address. With a static IP, you only need to whitelist this single IP address on your FTP server, improving security.

Step 4: Cost Management: You can optimize costs by powering off the Azure VM when it’s not in use. This can be done manually or automated based on your needs, ensuring cost-efficiency.

By adopting this alternative approach, you can simplify your setup, enhance security, and reduce the complexity associated with whitelisting a large range of IP addresses on your FTP server. This method can provide a more efficient and secure solution for your FTP operations within Azure DevOps.