-
Notifications
You must be signed in to change notification settings - Fork 394
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
Features does not work with proxy MITM certificate on windows #333
Comments
ℹ️ Looks similar to the issues reported in microsoft/vscode-remote-release#7648 |
I sadly have not been able to reproduce the issue yet. Are there any other details about your windows environment or network that you think could be useful to get a repro? (ie: Is this your personal computer, or corporate-managed, which version of Windows/VS Code/Dev Containers are you on?) Also, is this intermittent, or consistently ending up in the same state for you? Lastly, to help me gather more data, would you mind sending me the results of http://github-debug.com/ over email? (@github.com) |
Corporate-managed Windows 10 22H2. CA root certificates in question are distributed via GPOs to the Windows Local Machine Certificate Store. VS Code 1.74.2 , Dev Containers v0.268.0 pre-releae or v0.266.1 (no difference).
It consistently fails to the same state. The component in question does not seem to respect the setting "Application -> Proxy -> System Certificates". ?
Will send you an email, once I find it. ;-) |
@EagleIJoe does the solution mentioned in microsoft/vscode-remote-release#7648 (comment) work for you? |
It seems like I do have the same problem. Switching back to Dev Containers 0.255.4 works and I can use "Add Dev Container Configuration Files..." command again. I'm on a Win 10 21H2 Build 19044.2075 corporate managed system. Access to internet is through MITM proxy with managed certificates. |
I am on Windows, hence it does not apply. |
This seems related to: |
Since the introduction of 'features', I am unable to use VS code devcontainers as it does not seem to access the Windows certificate store to get the CA certificates.
Accessing the specified URL with any other application works.
The text was updated successfully, but these errors were encountered: