-
Notifications
You must be signed in to change notification settings - Fork 524
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
Private registry, self-signed certificate does not work: "can not verify first certificate" #497
Comments
Is this server on localhost? Thx. |
Hi,
I am using the python debugger running on my Windows machine. It is started from Visual Studio code. So yes, all running locally.
Regards,
Sebastian
Von: Stephen Weatherford (MSFT) <[email protected]>
Gesendet: Dienstag, 25. September 2018 22:10
An: Microsoft/vscode-docker <[email protected]>
Cc: Sebastian Schuette <[email protected]>; Author <[email protected]>
Betreff: Re: [Microsoft/vscode-docker] Private registry, self-signed certificate does not work: "can not verify first certificate" (#497)
Is this server on localhost? Thx.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#497 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ApbvcNTBLVo6mEilQ4MrzyCAvCOzgdc0ks5ueo2VgaJpZM4WySyO>.
|
I would like to see this addressed as well. I am not using a localhost. I am using a registry with a self-signed certificate and I am able to reach it through the browser but I get the same Error:self signed certificate message why trying to add the registry. |
Thanks, we're hoping to look into this soon. vscode doesn't currently have built-in proxy support for extensions. You can try setting "http.proxyStrictSSL" to false in settings and see if that fixes it for the moment, but that does carry security risks. |
Tracking this in #483 |
@aarongilliland @SebastianSchuette Could you please try the new functionality for trustede certificates and certificate stores and see if that works instead of setting http.proxyStrictSSL to false? Thanks. |
The feature "connect to private registry" does not work for a private registry with a self-signed certificate. You get an error "can not verify first certificate".
IMHO, having self signed certificates is very common for private registries.
The text was updated successfully, but these errors were encountered: