node.js - NPM install error Permission denied (publickey) for local repo

Question

Getting permission denied error for a local repo in my company github, which I can clone successfully, however getting error for NPM install:

npm ERR! Error while executing:
npm ERR! C:Program FilesGitingit.EXE ls-remote -h -t git@<repo path and name>
npm ERR!
npm ERR! Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128

Answer 1

I ran into this problem and was not able to fix as all the solutions lacked one important step, so I am posting my answer in greater detail.

Assuming you have already generated ssh-key and added its public key to your github account. Also, assuming you are using Windows-10.

npm install on Windows causes a lot of problems because there are ssh-agents running from 2 different sources:

• Windows provided ssh-agent (OpenSSH). This feature was added in one of the Windows-10 updates and is the culprit. :)
• Git ssh-agent (this one is required for your scenario)(assuming git is installed.)

Detect source of running ssh-agent

• Run start-ssh-agent (to run git provided ssh-agent) and ssh-agent (to run Windows provided ssh-agent) in cmd.

• Go to task manager and click on details tab.

• Look for ssh-agent.exe.

After following above steps, you can see 2 ssh-agent.exe running. In the 'User name' column you can see one for SYSTEM (this is provided by Windows) and one for your-user-name (this is git). Now, please close all ssh-agents you started for npm install(directly from task manager).

Cause of issue:

ssh-agent that npm install is trying to use is from the git but it is being conflicted with the windows provided ssh-agent.

Git ssh-agent can be started using start-ssh-agent but when you try to add ssh-key to your ssh-agent using command ssh-add -k ~/.ssh/id_rsa, it is trying to access ssh-add.exe from Windows path but not picking ssh-add.exe from git.

Solution:

Solution is to add ssh path of git to the Environment variables of your system and adding it before the "%SYSTEMROOT%System32OpenSSH" so it has higher priority.

This is only required so that you can access ssh-add.exe of git and after successful npm build you can freely remove it(even if you want to clone more repos and build them). Unless you want to add more keys for different repos.

Note: This path is different from the already present git/cmd path added during git installation so please make sure it is added before openSSh path variable for higher priority.

Please follow below steps to resolve your issue:

1. Start your git ssh-agent by running start-ssh-agent in cmd. Don't use ssh-agent as it starts the Windows provided ssh-agent.
2. Open Task Manager and go to Details tab.
3. Look for ssh-agent.exe.
4. Right click on ssh-agent.exe(on the one provided by git) and click open file location.
5. Copy the path and add it to Environment variables for system. Please make sure you move this path above "%SYSTEMROOT%System32OpenSSH".(Ignore if already present).
6. Close cmd and also close the running ssh-agent.exe from task manager. Note: Closing cmd is required for Env. variables to take effect.
7. Open cmd in your repo and run where ssh-agent and where ssh-add to test which ssh path will be preferred. (Hope you see 2 paths now and OpenSSH should not be appearing before Git/bin/usr path :) )
8. Now, you are done. Run start-ssh-agent.(Runs git ssh-agent)
9. Add your preferred ssh key to you ssh-agent by ssh-add -k ~/.ssh/id_rsa.(choose private key). (Adds keys to git ssh-agent, not Windows ssh-agent)
10. Once successfully added, run npm install.

Note: After this, whenever you see the same error again, just run start-ssh-agent and then npm install.

I hope it works, and if you are not comfortable, after successful npm build you can even remove the newly added path from env. variables as it was required only once(to access ssh-add from git), and start-ssh-agent is not accessed from that path.

Edit: It won't affect if you delete the path but I would recommend not to delete the path as this path also has many other useful tools like perl.exe, openssl.exe (don't need to install these tools separately).