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

Proxy issues when installing MS C# Extension (omnisharp) #14852

Closed
FloMaetschke opened this issue Nov 2, 2016 · 2 comments
Closed

Proxy issues when installing MS C# Extension (omnisharp) #14852

FloMaetschke opened this issue Nov 2, 2016 · 2 comments
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@FloMaetschke
Copy link

  • VSCode Version: 1.7.0-insider
  • OS Version: Windows Server 2008 R2

Steps to Reproduce:

  1. Use Visual Studio Code with Corporate Proxy

settings.json contains:

	// The proxy setting to use. If not set will be taken from the http_proxy and https_proxy environment variables
	"http.proxy": "http://user:[email protected]:8080",
	"http.proxyStrictSSL": false,
  1. Install C# Extension

Result:

Proxy works for Installation of Extensions and Update checking. The proxyStrictSSL works.
It seems that the OmniSharp Extensions Network Connection does not use http.proxyStrictSSL.

=> unable to verify the first certificate

The OmniSharp Log shows:

Installing OmniSharp to C:\Users\MYUSERNAME.vscode-insiders\extensions\ms-vscode.csharp-1.4.1\out.omnisharp-desktop
Attempting to download omnisharp-1.9-beta14-win-x64-net451.zip

The Debug Console of VSCode shows:

/C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121 [Extension Host] Uncaught Exception: Error: unable to verify the first certificatew.logExtensionHostMessage @ /C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121
/C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121 [Extension Host] Error: unable to verify the first certificate
at Error (native)
at TLSSocket. (_tls_wrap.js:1060:38)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket._finishInit (_tls_wrap.js:584:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)w.logExtensionHostMessage @ /C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121
/C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:126 unable to verify the first certificate: Error: unable to verify the first certificate
at Error (native)
at TLSSocket. (_tls_wrap.js:1060:38)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket._finishInit (_tls_wrap.js:584:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:126
/C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121 [Extension Host] Uncaught Exception: Error: socket hang upw.logExtensionHostMessage @ /C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:121

@rebornix
Copy link
Member

rebornix commented Nov 2, 2016

It's an OmniSharp issue and it's already logged there dotnet/vscode-csharp#579

@rebornix rebornix closed this as completed Nov 2, 2016
@rebornix rebornix added the *caused-by-extension Issue identified to be caused by an extension label Nov 2, 2016
@FloMaetschke
Copy link
Author

Thx, for the linked temporary workaround. I can now use omnisharp.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants