Connecting to AW EC2 instances using ssh

[kcording]

To connect to my AWS EC2 instances requires a SFTP SSH connection using a user password and key file . The remote connection setup in Wappler does not allow for a Key file to be loaded , but only a password.
What might be the solution here that I can use to connect to my AWS instances.

Thanks

[George]

Hi Kelvin,

We were just adding more options to the FTP connection options in Wappler.
Next to options for FTPS Implicit/explicit connections we will also add a keyfile for SFTP.

Hope to make it available in the update for today.

[George]

Using SFTP with key files in now available in the latest 1.0.5 version

[kcording]

There is now a failure with Authentication on AWS using SSH . ( V1.05) The connection protocol is asking for a continue (Y/N ) but no opportunity to reply hence connection failure returned.

[George]

Hi Kelvin,

Could you find out what ssh program you got installed and where it is?

Also in what OS are you exactly?

[kcording]

Running Windows Putty and filezilla. Both
connect to aws ec2 instances OK. Note in filezilla when connecting

.
Also both using private key created by putty and run on C drive programs files
Running win10
Hope this helps

[kcording]

Wappler SSH connection test error

[George]

Could you send me the Wappler debug log after you tried the ftp:

How to send us the Wappler debug log

We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. It is available in Wappler under the File / Submit error report … ot Alt+ctrl+p (or alt+cmd+p for mac) However it seems that it does not work for all users so here are instructions of where you can locate the debug log your slef so you can post it to the forum manually. for Windows it is located at: C:\Users\username\AppData\Local\Wappler\User Data\chrome_debug.log (make sure hidd…

Also could you start a Command prompt and see where is the SSH program located.
You can do this by clicking on the Windows Search button on the taskbar, type cmd in the search box and choose Command Prompt on the top.

In the command prompt type:

where ssh

then type:

ssh -v localhost

and let me know what the output is. Paste it here as screenshot

[kcording]

report_2018-5-24_22-11-2.zip (143.0 KB)
George two files as requested
Thanks

[George]

Thanks Kelvin - this is really helpful.

It seems you are using the new ssh command for connecting that Microsoft auto installed in the latest Windows 10 April update …

This command isn’t functioning very well however.

You can try to install the Git for Windows, to get a real good replacement for ssh:

Git for Windows Installation

For our Windows users - you might need to install Git for Windows 64 bits If you are willing to use SFTP or Git publishing Make really sure it is the 64 bits version Get it from https://gitforwindows.org/ Steps: First step is default: [image] This step is the most important! You should choose to add to your PATH [image] The rest is all default … [image] [image] [image] [image] [image]

Make sure you don’t skip the add to path section.

Afterwards you can check with the command prompt as above, the “where ssh” should point to the github for windows installation.

If not - try reordering the PATH in the system environment settings.

[kcording]

Carried out these steps.

See result

[George]

oh I see there is some conflict with the cygwin DLL as the error indicates. Seems you have more of it and conflicting versions.

Maybe try to clean those out see what other software you have installed.