-
Notifications
You must be signed in to change notification settings - Fork 178
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #101 from pressly/common-ssh-issue
Update README.md
- Loading branch information
Showing
1 changed file
with
26 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -285,6 +285,32 @@ Top-level Supfile calls `sup` with Supfiles from sub-projects: | |
sup -f ./database/Supfile $SUP_ENV $SUP_NETWORK up | ||
``` | ||
|
||
# Common SSH Problem | ||
|
||
if for some reason sup doesn't connect and you get the following error, | ||
|
||
```bash | ||
connecting to clients failed: connecting to remote host failed: Connect("[email protected]"): ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain | ||
``` | ||
|
||
it means that your `ssh-agent` dosen't have access to your public and private keys. in order to fix this issue, follow the below instructions: | ||
|
||
- run the following command and make sure you have a key register with `ssh-agent` | ||
|
||
```bash | ||
ssh-add -l | ||
``` | ||
|
||
if you see something like `The agent has no identities.` it means that you need to manually add your key to `ssh-agent`. | ||
in order to do that, run the following command | ||
|
||
```bash | ||
ssh-add -K ~/.ssh/id_rsa | ||
``` | ||
|
||
you should now be able to use sup with your ssh key. | ||
|
||
|
||
# Development | ||
|
||
fork it, hack it.. | ||
|