To view the more detailed error messages, you can do the following:ĭownload and install the free Fiddler Web Debugging Proxy by Telerik (one of my favorite tools)Ĭlose all browsers and other applications, then run Fiddler Details: BadGateway” error are available in the asynchronous HTTP conversation between the PowerAutomate web front end (UI) and backend. Thanks to an incredible tip from ScottB, I recently learned that additional details about the generic “Test connection failed. The general SFTP connector error: Test connection failed. It generally throws a single error message when creating new SFTP connections if something is amiss. The “SFTP - SSH” connector (in my experience) does not provide incredibly meaningful error messages in the user interface (although this is improving over time). If using SSH host key fingerprint validation, ensure the finger print is formatted properly (MD5).Ensure your private key is PEM (OpenSSH) formatted (and NOT PuTTY Private Key File /.Allow MS Power Automate’s (Flow’s) source IP addresses ( Connectors section) through your firewall.Ensure PowerAutomate can resolve your SFTP server’s hostname using DNS.Ensure you are using the correct credentials.Read on for more detailed information about these tips - they apply to the SFTP - SSH connector: Of this, I wanted to share some of my findings in hopes they will be of value to someone else. With its support of SSH key-based authentication and SSH/SFTP ports besides 22 (the default). In Microsoft Power Automate (Flow) has quickly become my personal favorite. This post was revised in late 2019 to reflect and capture the changes. There are configuration and functional differences between the old and new connectors. All product names, logos, and brands used in this post are property of their respective owners.Īs of late 2019, the original Flow SFTP connector is deprecated in favor of the new Power Automate SFTP - SSH connector.

Filezilla ssh gateway interactive