Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

491
Views
Unable to used private repo in npm dependencies

Hey Guys I am geting this error when running npm install

openssl config failed: error:02001002:system library:fopen:No such file or directory
openssl config failed: error:02001002:system library:fopen:No such file or directory
npm ERR! Error while executing:
npm ERR! C:\Users\rmittal\AppData\Local\Programs\Git\cmd\git.EXE ls-remote -h -t ssh://git@github.com/xxxx/xxx-api.git 
npm ERR!
npm ERR! Host key verification failed.
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

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\rmittal\AppData\Roaming\npm-cache\_logs\2021-04-02T06_15_51_313Z-debug.log

git@github.com/xxxx/xxx-api.git is my other repo only I looked into npm install error : "Host key verification failed." but did not lead me to solution. Can someone plz help me?

Version used :

D:\>node -v
v10.23.1

D:\>npm -v
openssl config failed: error:02001002:system library:fopen:No such file or directory
openssl config failed: error:02001002:system library:fopen:No such file or directory
6.14.10

Repostiory are also setup properly

over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

A ssh-keyscan -H github.com >> ~/.ssh/known_hosts suggested in the answer you mention should work, but since you are in a CMD, it should be:

ssh-keyscan -H github.com >> %USERPROFILE%/.ssh/known_hosts

Assuming:

  • your %PATH% includes C:\path\to\Git\usr\bin (where ssh-keyscan.exe resides)
  • your private key does give you access to that private repository.

Test the last point with (independently of npm), in any folder

 git ls-remote git@github.com/xxxx/xxx-api.git

If you can list remote heads from that private repository, that means you do have access to it. And it should ask to add a fingerprint in %USERPROFILE%/.ssh/known_hosts if needed.

Then you can try the npm command again.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!