Connection failed about flightplan

[Serhioromano]

@rriosarias First I made like this

plan.target('production', {
    host: '54.145.**.**',
    username: 'deploy',
    password: '*********',
    agent: process.env.SSH_AUTH_SOCK
});

But that was not secure to upload this settings to github. What I did I created id_rsa certificate. Uploaded publick key to server. And pointed my private.

plan.target('production', {
    host: '54.145.**.**',
    username: 'deploy',
    privateKey: '/Users/Sergey/.shh/id_rsa',
    agent: process.env.SSH_AUTH_SOCK
});

And this way it also connect but I do not need to expose my password.

Just make sure that you can connect to your server SSH without the password being asked.

[artdevjs]

I had error with authentication, sounds like "All configured authentication methods failed".
But I solved this by adding path to the privatekey in the connection config.

plan.target('staging', [{
        host: host,
        username: username,
        privateKey: 'path/to/the/.ssh/id_rsa',
        agent: process.env.SSH_AUTH_SOCK
    }
]);

[pstadler]

Try .ssh/ instead of .shh/

Cheers,
Patrick

[Serhioromano]

Figured that out. I had to add password.

[rolo-js]

Hi, I have the same problem... Where or what did you add password to?
Thanks.

[rolo-js]

Fantastic! Thanks.
FYI, while experimenting, I discovered that you can also use the path to the rsa key in the "agent" property instead of the .SSH_AUTH_SOCK value.

Regards.

[pstadler]

Here's an article regarding adding keys to ssh-agent for passwordless authentication: https://help.github.com/articles/working-with-ssh-key-passphrases/

[neilhanekom]

Hi Guys,

I am having the same issue here. I have added my rsa_id keys prior to this. So I can connect to my server without password.

Now adding privateKey key/pair to the production object as you have suggested gives me the following line:

Warning: Identity file /Users/neilhanekom/.shh/id_rsa not accessible: No such file or directory.

This is probably a permission/role issue. But I would greatly appreciate if anyone can help me on this.

[romanostolosh-devpronet]

Hi everyone,

Cool tool. Just wanted to say that.

One thing that I found inconvenient though is that you still have to provide privateKey, username and so on, regardless the fact that we may have fully functional and configured ssh client localy..

What I'm trying to say is that it would be really cool if we were able to make use of ~/.ssh/config file that user may already have configured

Is it even technically possible?

Thank you in andvance

[pstadler]

@romanostolosh-devpronet check this: mscdex/ssh2#70

[romanostolosh-devpronet]

@pstadler thanks!
Sounds like a plan :)

[ALEXOTANO]

I had error with authentication, sounds like "All configured authentication methods failed".
But I solved this by adding path to the privatekey in the connection config.

plan.target('staging', [{
        host: host,
        username: username,
        privateKey: 'path/to/the/.ssh/id_rsa',
        agent: process.env.SSH_AUTH_SOCK
    }
]);

Works perfectly, just careful not tu use ~/.ssh/key use the whole path.

[MohamedNedal]

I had error with authentication, sounds like "All configured authentication methods failed".
But I solved this by adding path to the privatekey in the connection config.

plan.target('staging', [{
        host: host,
        username: username,
        privateKey: 'path/to/the/.ssh/id_rsa',
        agent: process.env.SSH_AUTH_SOCK
    }
]);

Where should I write this please?