-
Notifications
You must be signed in to change notification settings - Fork 304
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
Handle Proxy Issues on Remote #231
Comments
Can you please try installing again and share us the remote server logs. You can find them by running the command
|
Seems to be a certificate problem with our company proxy. Is it possible to disable certificate checking for VSCode remote extension installing? Setting |
Yeah this is known proxy issues and above settings will not help on remote. @chrmarti How can we handle the proxy issues on remote given that we do not have access to electron? |
@chrmarti This is not remote ext host.. this is remote ext management not sure if we do same w.r.to proxies |
@chrmarti Certificates should be installed OK as tests with curl and wget shows. If there is anything I can test additionally let me know. |
@sandy081 Then we don't load the credentials from the OS. Wouldn't that be the same with the local extension management? We should look into bringing that on par with the extension hosts. |
Local extensions management is an electron process which uses chromium network stack. We cannot bring them on par unless we also use electron on remote which we do not want. Other solution which is in the plate from beginning is to stream installation from local to remote. It means download it on renderer and stream it to remote. |
Got it. So one other direction would be to reuse the proxy and certificates code I've written for the extension host in proxyResolver.ts for the remote extension management. |
yeah makes sense |
Same problem here; company proxy with internal certificates, leading to a 'unable to get local issuer certificate'. Would be nice if it was possible to configure this properly for the remote side (both the proxy and certs, in case they can't be properly picked up automatically). Plus, an option to ignore certificate validation for the remote side. |
Recently update to VSCode 1.35.0. Attempted to install a few extensions as noted by other users. I am running VSCode on Windows 10 and ssh into a CentOS box. I do have the proxy configuration (i.e., "http:proxy" set so extensions, mainly CPP Tools, can be installed properly. Would it be possible for VSCode to picked up the proxy, if set, on the local side and use them on the connecting side? |
Perhaps outside the scope of this item, but will VSCode be able to install the extension I enabled on the host side (local) to the remote side automagically? I am wondering if I will need to install the extension each time connecting to the remote machine. I am not sure this is the case since I can't install any extensions at the moment. |
I know this topic is close, but VSCode 1.36 just came out and Remote-SSH also updated. I retried setting up a remote editing session then tried to install the C/C++ extension. It did download and install correctly. Even went through the C/C++ insiders updating. Thanks for getting this to work. Now, just need to start editing files and see if the rest of it works.
Edit: I have noticed that I keep getting the C/C++ Extension has been updated notification even after I press the button to reload. |
This issue is about downloading extensions and what you are seeing is downloading the server. Can you please file a separate issue and let us know which remote extension are you using? |
@kmalloc In my case, I could solve that issue by adding
I hope it could help you |
Steps to Reproduce:
After creating the remote connection I try to install an extension which results in the above notifications.
The text was updated successfully, but these errors were encountered: