Skip to main content

Notifications

Community site session details
Power Automate - Using Connectors
Answered

SFTP SSH connector BadGateway

Like (0) ShareShare
ReportReport
Posted on 24 Mar 2023 19:45:00 by 30

Hi Power Automate community!

 

I get this error when trying to connect to an S3 bucket. All the credentials are correct, and I am able to connect using terminal. But Power Automate doesn't want to connect. I checked with my company's network department, and they confirmed that the Firewall is not blocking this connection. Could you please advise?

Capture.PNG

  • Suggested answer
    AWildes Profile Picture
    4 on 13 Nov 2024 at 16:22:18
    SFTP SSH connector BadGateway
    I am still working on this. However, I would like to share this recent finding.  I am using the SFTP - SSH connector to connect to a third party vendor's SFTP site using password authentication.  I was running into this very same issue.  The connector creation worked fine.  When configuring the connector I was able to choose the folder on the Vendor's SFTP site, yet when I ran the cloud flow, I was receiving an invalid connection/Bad Gateway error.  I stumbled upon updating the Action timeout and the Retry settings of the connector.  Once I updated these from the default values to values of my own my flow worked.   As stated, I am still testing this theory for consistency.  For the first 4 runs, I have no longer received the Bad Gateway error.   The times must be in ISO 8601 format to work in both settings.    I hope my findings may help someone as this, thus far, has been helping me.
     




    11/13/2024 4:04pm -  **UPDATE**  I think it was a coincidence that when I made the change to the action timeout and the retry policy that all appeared to be working.  This is still an issue with this connector.  I find it very odd that I can set the connection  and use the UI to chose the folder (meaning that the only way I am able to see the SFTP site folders is via the account username/password authentication).  Yet Upon saving or even running the flow, it fails with a BAD GATEWAY error it is very odd.    I am able to go to connections, update my connection using the same credentials and they save just fine.   So I am not sure why SFTP connector is unable to use a connection that works.   
  • collinnunis Profile Picture
    25 on 07 May 2024 at 11:21:44
    Re: SFTP SSH connector BadGateway

    Thanks! I followed these tips after getting the network admin to whitelist the public IP addresses. This solved my issues. 

  • naidu1811 Profile Picture
    103 on 01 May 2024 at 10:37:02
    Re: SFTP SSH connector BadGateway

    kudos  @dani135 ,Its working for me.

    1. The connection name can be anything but try to name it something that you will immediately recognize, especially if you plan to have multiple SFTP SSH connections in the future.

    2. The host server address is the URL of your server that you set up using the Transfer Family. Please refer to these tutorials: https://www.youtube.com/watch?v=3_HHSnoFsoM, https://docs.aws.amazon.com/transfer/latest/userguide/getting-started.html 

    3. The ‘User name’ is the name that you created during the previous step when you set up your server.

    4. Leave the password field empty.

    5. The SSH private key is a key that you can generate from your computer’s terminal using this command - ssh-keygen -m PEM -t rsa -b 4096 -f name-of-the-key. Please keep in mind that you can find your keys in this directory: ‘C:\Users\<your username>’. The public key will have the ‘.pub’ extension and the private key will not have any extension. But you can open both using a text editor of your choice. Copy the contents of the private key into the ‘SSH private key’ field and copy the contents of the open key into your server. It’s essential that both keys are in place before you establish your SFTP - SSH connection.

    6. If you had generated a passphrase during the previous step, enter it in the ‘SSH private key passphrase’ field.

    7. Enter port number 22.

    8. Disable the SSH host key validation.

    9. Leave SSH host key finger-print empty.

    10. In the ‘Root folder path,’ enter your bucket name like this: ‘/your_bucket_name/folder/'

    11. Click ‘Create.' If you encounter an error, check that your RSA private key is correct (it must start with ‘BEGIN RSA PRIVATE KEY’) and that your root folder path contains a forward slash before the bucket name. If you still can’t connect, check that you spelled the host server address correctly and that your user has sufficient permissions to access and read from the bucket.

  • Verified answer
    dani135 Profile Picture
    30 on 09 Apr 2024 at 17:03:05
    Re: SFTP SSH connector BadGateway

    I don't think I whitelisted those IP addresses before doing this. But anyone who is still struggling with this SFTP SSH connector, please try these steps:

    1. The connection name can be anything but try to name it something that you will immediately recognize, especially if you plan to have multiple SFTP SSH connections in the future.

    2. The host server address is the URL of your server that you set up using the Transfer Family. Please refer to these tutorials: https://www.youtube.com/watch?v=3_HHSnoFsoM, https://docs.aws.amazon.com/transfer/latest/userguide/getting-started.html 

    3. The ‘User name’ is the name that you created during the previous step when you set up your server.

    4. Leave the password field empty.

    5. The SSH private key is a key that you can generate from your computer’s terminal using this command - ssh-keygen -m PEM -t rsa -b 4096 -f name-of-the-key. Please keep in mind that you can find your keys in this directory: ‘C:\Users\<your username>’. The public key will have the ‘.pub’ extension and the private key will not have any extension. But you can open both using a text editor of your choice. Copy the contents of the private key into the ‘SSH private key’ field and copy the contents of the open key into your server. It’s essential that both keys are in place before you establish your SFTP - SSH connection.

    6. If you had generated a passphrase during the previous step, enter it in the ‘SSH private key passphrase’ field.

    7. Enter port number 22.

    8. Disable the SSH host key validation.

    9. Leave SSH host key finger-print empty.

    10. In the ‘Root folder path,’ enter your bucket name like this: ‘/your_bucket_name/folder/'

    11. Click ‘Create.' If you encounter an error, check that your RSA private key is correct (it must start with ‘BEGIN RSA PRIVATE KEY’) and that your root folder path contains a forward slash before the bucket name. If you still can’t connect, check that you spelled the host server address correctly and that your user has sufficient permissions to access and read from the bucket.

  • collinnunis Profile Picture
    25 on 09 Apr 2024 at 08:36:09
    Re: SFTP SSH connector BadGateway

    Hi there, I am also trying to do the same thing - connecting to an S3 bucket using Power Automate. Can I confirm that you needed to whitelist the IP addresses of Power Automate (https://learn.microsoft.com/en-us/connectors/common/outbound-ip-addresses#power-platform) in the firewall to allow this to happen? 

  • Valcoren Profile Picture
    6 on 20 Mar 2024 at 17:59:02
    Re: SFTP SSH connector BadGateway

    I have been running into the same issue with connecting to SFTP with a cloud triggers. Its random when it happens forcing a retrigger until it pushes through. I've broken up all parallels to down to a single action still and still experience random connection issues. 

  • lbendlin Profile Picture
    7,822 Super User 2025 Season 1 on 06 Mar 2024 at 12:16:10
    Re: SFTP SSH connector BadGateway

    Can you set the parallelism for that action to 1?

  • speakup Profile Picture
    10 on 06 Mar 2024 at 11:02:20
    Re: SFTP SSH connector BadGateway

    This blog describes how to see the error behind the BadGateway shown. Basically:

    1. open DEV tools (F12) in the browser.
    2. navigate to Network
    3. click the "Folder" request in the left pane
    4. click Preview and look for inner error

    JohnMo11_0-1709722832819.png

    Mine says
    "An existing connection was forcibly closed by the remote host"

     

    This is probably due to Power Automate creating simultaneous connections to the server. I've not been able to find out how to solve this. Connection with WinSCP is working without problems.

  • YazeedAblan Profile Picture
    82 on 06 Sep 2023 at 09:30:28
    Re: SFTP SSH connector BadGateway

    Hello, any solution for this one ?

  • dani135 Profile Picture
    30 on 31 Aug 2023 at 17:21:54
    Re: SFTP SSH connector BadGateway

    Hello,

     

    Could you share a screenshot of your current setup with sensitive info greyed out? What service are you trying to connect to (S3)?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Power Automate - Using Connectors

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 8 Super User 2025 Season 1

#2
lbendlin Profile Picture

lbendlin 7 Super User 2025 Season 1

#3
KT-07051015-0 Profile Picture

KT-07051015-0 4

Overall leaderboard

Featured topics