-
Notifications
You must be signed in to change notification settings - Fork 24
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
How to skip certificate validation? #104
Comments
I'm getting Error: certificate signature failure when trying to connect to a asp.net site using .Net 6 and VS 2022 preview running in debug mode locally. |
I also have the same issue on my end on localhost with https:
|
Similar for me - I have a suite of microservices running in docker with ports exposed to localhost, and I use a locally generated certificate for SSL. I get "Error: unable to verify the first certificate" rather than the "Error: Self signed certificate" that others get. |
My error is slightly different, but same issue - need a way to skip SSL validation. Error: |
Hello, any update on this? BTW: I've seen both errors "self signed certificate" and "unable to verify the first certificate" on different services |
My really hacky workaround was to add this line: As the first line of this file: If the extension gets an update I assume it will wipe out your change. It seems like a huge oversight to not have an option to ignore cert warnings. Especially considering how common it is to use self signed certs during the development phase of REST APIs. |
The above hack worked for me as well. However, it would be great to have a proper solution. The vscode extension Rest Client apparently knows how to do it. Maybe guided by this article on Stack Overflow: Error: unable to verify the first certificate in nodejs. |
I have a development website that uses a self-signed certificate for HTTPS. Thus I get the following:
Error: self signed certificate
How can I skip certificate validation?
What is the mechanism used to validate certificate?
The text was updated successfully, but these errors were encountered: