question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] ##[error]unable to get local issuer certificate

See original GitHub issue

Describe the bug

The action is no longer connecting to our Vault server.

To Reproduce

  1. Add your build.yaml workflow
  2. Add this step:
- name: Import Secrets from Vault
  id: vault_secrets
  uses: hashicorp/vault-action@master
  with:
    url: ${{ secrets.VAULT_ADDR }}
    method: github
    githubToken: ${{ secrets.VAULT_ACCESS_TOKEN }}
    kv-version: 2
    exportEnv: false
    secrets: |
      mysecret MY_SECRET;

Note: The vault address’s SSL cert is still valid until next year

Expected behavior

It will then show an error: ##[error]unable to get local issuer certificate

Log Output

##[debug]'
##[debug]Loading env
Run RichiCoder1/vault-action@master
  with:
    url: ***
    method: github
    githubToken: ***
    kv-version: 2
    exportEnv: false
    secrets: mysecret MY_SECRET;
  
    tlsSkipVerify: false
::group::Test Get Vault Secrets
Test Get Vault Secrets
  
  
  ##[debug]Retrieving Vault Token from v1/auth/github/login endpoint
  ::endgroup::
##[error]unable to get local issuer certificate
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Import Secrets from Vault

Additional context

We managed to fix it by sticking to the previous working version: RichiCoder1/vault-action@v1.0.1 or hashicorp/vault-action@v1.0.1 and not using master version

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:16 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jasonodonnellcommented, Aug 13, 2020

@tamipangadil Was your original issue resolved with newer commits of vault-action? Looking to close this issue.

0reactions
tirelibirefecommented, Dec 4, 2022

nope, the problem still exists in Dec.2022. TLS enabled Vault doesn’t work on EKS.

http: TLS handshake error from 10.61.20.41:33356: remote error: tls: bad certificate

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix "Unable to get Local Issuer SSL Certificate" Error?
Reason for “Unable To Get Local Issuer Certificate” Error​​ This error indicates that the root certificate is not functioning correctly when a  ......
Read more >
SSL certificate problem: Unable to get local issuer certificate
A Self-signed certificate cannot be verified. Default GIT crypto backend (Windows clients). Resolution. Resolution #1 - Self Signed certificate. Workaround.
Read more >
error unable to get local issuer certificate #841 - yarnpkg/yarn
On Windows I solved the issue by adding the following environment variable: NODE_EXTRA_CA_CERTS=C:\path\to\ca.pem where ca.pem is the chain ...
Read more >
PHP - SSL certificate error: unable to get local issuer certificate
Download the certificate bundle. · Put it somewhere. In my case, that was c:\wamp\ directory (if you are using Wamp 64 bit then...
Read more >
Visual Studio 2017: SSL certificate problem: unale to get local ...
I have a corporate/self-signed Cert on my TFS instance. Git failed with a fatal error. fatal: unable to access 'https://tfs/tfs/myproject/_git/myrepo': SSL ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found