Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On-Premise certificate error #6

Closed
yondersever opened this issue Nov 12, 2020 · 3 comments
Closed

On-Premise certificate error #6

yondersever opened this issue Nov 12, 2020 · 3 comments

Comments

@yondersever
Copy link

I'am getting following error when I refresh apis and domains. Because of that error list is not filled.

Error:

request to (url) failed, reason: unable to verify the first certificate

@photchkiss
Copy link

Getting the same error. I am wondering if there is a way to provide a cafile or something that includes certificates not signed by a Global CA?

@hkosova
Copy link
Contributor

hkosova commented Nov 17, 2020

This answer suggests adding the trusted certificates (root + intermediate) to the operating system's certificate store:

According to https://code.visualstudio.com/docs/setup/network, the solution is to edit the system certificate store:

Since Chromium uses the OS's certificate trust infrastructure, the preferred option is to add your proxy's certificate to your OS's trust chain.

This means that your answer is OS-dependent:

  • Windows: Powershell Import-Certificate or the GUI equivalent
  • Mac: Via Keychain Access
  • NSS under linux - it is unclear which NSS database it uses. certutil is used to edit them.

Can you try and see if this resolves the issue?

@yondersever
Copy link
Author

This answer suggests adding the trusted certificates (root + intermediate) to the operating system's certificate store:

According to https://code.visualstudio.com/docs/setup/network, the solution is to edit the system certificate store:

Since Chromium uses the OS's certificate trust infrastructure, the preferred option is to add your proxy's certificate to your OS's trust chain.

This means that your answer is OS-dependent:

  • Windows: Powershell Import-Certificate or the GUI equivalent
  • Mac: Via Keychain Access
  • NSS under linux - it is unclear which NSS database it uses. certutil is used to edit them.

Can you try and see if this resolves the issue?

It solved my problem.
Thanks for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants