SFTP - SSH Connector - Invalid private key file

[liveopsBI]

Hello Community,

I have come to a head. The SFTP - SSH connector does not seem to be accepting any valid private keys.

provided host, private key in the same format described on this page https://docs.microsoft.com/en-us/azure/connectors/connectors-sftp-ssh#connect and this page, https://blog.neilsabol.site/post/microsoft-ms-flow-sftp-connector-tips-tricks-errors/. I receive and error everytime

Invalid private key file

The connection works in Filezilla and other sftp clients. Power Automate is the only place where this setup is not working.

I have attempted using the username in the SSH passphrase

I have attemopted encrypting with a pasphrase

I have attempted enabling Disable SSH host key validation

Any help would be greatly appreciated. 

link to a screenshot

https://drive.google.com/file/d/1Pbxhw9FCsjwrrLM4deS3PGp2Xq658wfr/preview 

[v-alzhan-msft]

Hi @liveopsBI ,

Could you please share a screenshot of the configuration of the connection?

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[liveopsBI]

I edited my original post with this link

https://drive.google.com/file/d/1Pbxhw9FCsjwrrLM4deS3PGp2Xq658wfr/preview 

[liveopsBI]

Anyone have any experience with a successful use of ssh key with the sftp-ssh connector?

[liveopsBI]

My issue is similar to this comment

https://blog.neilsabol.site/post/microsoft-ms-flow-sftp-connector-tips-tricks-errors/#comment-474219...

my issue is similar in that I too am using AWS Transfer. 

This is from that blog post that gets referenced on this forum quite a bit. The blogger's reply is revealing - 

"

You raise a good question. There is definitely something amiss with SFTP interop between Power Automate and the AWS Transfer for SFTP service. I was able to reproduce the same issue as you. I can connect to the AWS Transfer service using key based auth from both WinSCP (ppk formatted) and a Linux machine (OpenSSH formatted, using the sftp command) without issue, but an SFTP connection using the same keys fails from Power Automate.

Another interesting data point is that Power Automate CAN connect via SFTP (using key-based auth) to AWS EC2 Linux instances.

I recommend raising a ticket to the Power Automate team about this one (https://flow.microsoft.com/... --> Contact Support, note URL may vary by region). At the very least, I am hoping support can provide a more specific error message.

The product issue mentioned in the previous comments is old (and resolved) but this may be a new one. The old product issue for reference and since I removed it from this post was:

Around October/November 2018, there was a product issue with Flow that prevented creating SFTP connections that use private keys (regardless of the formatting considerations described in this post). In this case, it had to do with Flow's front end handling of multi-line text. This was partially addressed by the Flow team the week of November 12, 2018; by "partial resolution" I mean that it was still necessary to use the correct method to create an SFTP connection in Flow. 1 way worked, another did not.

Creating an SFTP connection (key based auth) from within the Flow editor (after adding an SFTP action to a flow) WORKED

Creating an SFTP connection (key based auth) from Settings -> Connections DID NOT WORK.

I am interested to hear if Microsoft comes back with anything. Good luck and I hope you are able to get the issue resolved. Thanks again!

"

Is anyone from Microsoft working on this?

[liveopsBI]

Is there anyone who has had success using a SSH key from a SFTP service hosted on AWS using the SFTP-SSH connector?

[maskeny · Accepted solution]

After many failed attempts I was finally able to make an SSH connection from Flow following the above message.

You have to create the SSH connector while creating a Flow, don't try to add the connector first.

Thanks.

[MSP_TEK]

I am not able to see the solution.  It would be MUCH appreciated if you can re-post or elaborate how you overcame this issue.  I am connecting to AWS Transfer SFTP server as well

[liveopsBI]

Posted at midnight.. I know what that's like. 

The solution is-

• Create the connector while you in the flow designer view,
• choose any SFTP-SSH connector trigger or action
• If you have never set one up, it will show in the correct view, otherwise, select the three dots and select add connection
• setup the connection in that view, be sure to specify the S3 bucket name as a part of the root folder path, specify your port (22), and disable SSH validation

If you mess up, the connection will be saved either way, and be stored in the connections list until you delete it, so try to get it right the first time, and if you get it wrong, it may be prudent to clean as you go. 

[claudiagrajeda]

i am following your steps, but i get a BadGateway error still, do you know what a i ma doing bad?