Can't Connect to SFTP

(0) Share

Report

Posted on by tmoss

Trying to create an SFTP connection:

Notably:

I can ping and telnet sFTP without issue
I can access sFTP via FileZilla without issue
I've referenced the blog post here: https://blog.neilsabol.site/post/microsoft-ms-flow-sftp-connector-tips-tricks-errors/ to make sure I was doing things correctly, did not help
I've tried enabling the Host Key Validation and entering the finger-print, did not help
I've tried leaving the root folder path blank, did not help
I've reviewed other posts (including: https://powerusers.microsoft.com/t5/Connecting-To-Data/SFTP-SSH-Test-Connection-Failed/m-p/591139) but could not find a solution that worked for me

Any help would be greatly appreciated.

Categories:

Using connectors

I have the same question (0)

All responses (8)

Answers (0)

Sort by

nihkel 65 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @tmoss ,
I've been exactly where you are now for the past few days trying to figure out where was my mistake.
Today it finally worked.

For me, the tricky part was getting the unespecific 'Bad Gateway' error over and over.
I'm using fingerprint validation too (wich was also kinda tricky).

At a first glance, the only thing I see different in your setup is the root.
I've used \ instead of /, so it may seem silly, but I recommend you try that given how picky this connector is.

The other parts that gave me some trouble were the SSH key formatting, but as far as I can see, you seem to be using the right one.
I found a bit confusing the part in the reference blog post you mentioned regarding the format, but I managed to get the RSA formatted key (like the one you have)
(I've also found out that if the key is wrong, there is a specific error message stating it, so you should be good there).

Also if you want to use fingerprint, note the format should be MD5, something like:
xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
instead of: ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(there is also a specific error message for a wrong format fingerprint)

I hope this can help you somehow,
Best regards

Was this reply helpful? Yes No
tmoss 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Really appreciate the suggestion @nihkel. It's one of the few responses I've gotten and the only one that provided a new potential solution to try.

Unfortunately, the \ instead of / still did not work for me 😞

Very disheartened and basically given up on using the platform.

Was this reply helpful? Yes No
nihkel 65 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm sorry to hear that @tmoss !
I'd encourage you to not give up. I really feel your frustration, I was just where you are a couple days ago thinking "this has to be a joke, how can this MS product be soooo not ready? Where is the support for it? Is noone actually able to use this connector? it can't be!"
After all it seems that It was me doing something wrong (I'm not entirely sure what..but I believe it was the SSH key/passphrase/fingerprint).
Documentation for this could (and should) be improved TREMENDOUSLY......!!

Since you are able to connect to the sFTP via FileZilla, that's probably using a .ppk file, right...?
How confident are you with the key conversion you've made? And the passphrase for the key?
Just as a sanity check, this is what I would try:
- open puttygen (included with winSCP or available in the putty official page)
- load your current key into it
- save it as if it was a new one you just generated (both public and private keys)
- double check the format of the key, it should be somethig like this.
- make sure you are able to connect via FileZilla/WinSCP to the server using you NEW keypair (setup a new connection in FZ as if it was a new connection)
If that works... the key is surely not to blame.

I really hope you can find the issue or someone else can help you further,
Good luck!

Was this reply helpful? Yes No
tmoss 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the encouragement @nihkel

I'm fairly confident in the key conversion and passphrase - as you mentioned, there is a specific error message if there is an issue there - but double-checked using the steps you laid out anyway and was still able to connect in FileZilla.

Seems the issue lies elsewhere yet.

Was this reply helpful? Yes No
nihkel 65 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi again,
yes, that's what I meant. Sorry if I didn't explain properly.
I think my case was a bit different since I was provided a .ppk for connectign to a partner SFTP server and had to do some key conversions myself (which I tested converting back again to a new .ppk).

Lets hope someone with more knowlegde than myself (should be pretty easy :D) can shed some light to your issue,
Best wishes

Was this reply helpful? Yes No
mohsinkhalid 160 on at

Like
a
(0)

Report
Copy link

Link copied!

Is this a public sftp point? If there are some network polices in place you can get the list of IP's from here to make sure you have white list the correct set of IP's base on your Environment region.

Was this reply helpful? Yes No
PowerUnicorn 9 on at

Like
a
(1)

Report
Copy link

Link copied!

OMG The back slash totally worked for me! Thanks!

Was this reply helpful? Yes No
Tony Fussell 5 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks.. The tip to get rid of the "ssh-rsa 2048" for the MD5 fingerprint got me working.

Was this reply helpful? Yes No