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

end of central directory record signature not found during extension install #2384

Closed
joaomoreno opened this issue Jan 26, 2016 · 91 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@joaomoreno
Copy link
Member

Related to #69

@joaomoreno

To confirm @takuan-osho @JFLavidalle @vilinski: Do you get the end of central directory record signature not found error when you try to browse extensions or when you try to install an extension?

@takuan-osho

@joaomoreno When trying to install an extension in my case.

@vilinski

@joaomoreno me too, trying to install, browsing works always

@JFLavidalle

@joaomoreno Browsing always works but installation failed.

Ping @maritz

@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Jan 26, 2016
@joaomoreno joaomoreno self-assigned this Jan 26, 2016
@maritz
Copy link

maritz commented Jan 27, 2016

Thanks!

Is there any way we can assist in debugging this? Can you replicate it somehow?

I face this problem while sitting behind a corporate proxy that requires a custom root cert to be installed.

@joaomoreno joaomoreno modified the milestone: Backlog Jan 27, 2016
@joaomoreno
Copy link
Member Author

@maritz Just to confirm, did you try this build?

@vilinski
Copy link

I'm also behind corporate proxy with authentication. It works at home, but no luck with installing any extensions on work PC.
Couldn't download the linked build

@maritz
Copy link

maritz commented Jan 27, 2016

@joaomoreno I have not. I would need a linux x64 build to test it, though.

@vizeke
Copy link

vizeke commented Jan 27, 2016

+1 same here. "end of central directory record signature not found"

Version 0.10.6

@joaomoreno
Copy link
Member Author

Ok. We're in the middle of releasing 0.10.7. Please give it a try with that release and let's tackle it then if not fixed.

@vizeke
Copy link

vizeke commented Feb 2, 2016

It's working on 0.10.7-insider

@joaomoreno
Copy link
Member Author

Excellent news. @takuan-osho @JFLavidalle @vilinski, maybe you guys can let us know if the issue's fixed for you as well?

@vilinski
Copy link

vilinski commented Feb 5, 2016

still no version update this week?

@egamma
Copy link
Member

egamma commented Feb 6, 2016

The plan is to push the next stable version 0.10.8 next Monday.

The insiders 0.10.7 version is already available, pls see https://blogs.msdn.microsoft.com/vscode/2016/02/01/introducing-insiders-builds/

@JFLavidalle
Copy link

@joaomoreno : I can confirm that the issue is fixed for me on release 0.10.7-insider.
Great news !

@joaomoreno
Copy link
Member Author

OK, got confirmation from 2 people that it is fixed, so closing this. Thanks!

@vilinski
Copy link

vilinski commented Feb 9, 2016

confirm working with stable and insiders builds. Finally can install extensions

@thoros1179
Copy link

For me the issue is NOT fixed. I tried 0.10.8 and 0.10.8 Insider.
"end of central directory record signature not found" still persists. I am behind corporate proxy.
I uninstalled previous versions of VS Code before installing.
What can I do to get around this issue?

@joaomoreno
Copy link
Member Author

@thoros1179 Did you configure the http.proxy and http.proxyStrictSSL settings?

@thoros1179
Copy link

I configured http.proxy and https.proxy. The extensions can be browsed but fail to install. I also tried http.proxyStrictSSL: false but it doesn´t change anything. The error persists.

vscode

@joaomoreno joaomoreno reopened this Feb 17, 2016
@joaomoreno joaomoreno modified the milestones: Feb 2016, Backlog Feb 17, 2016
@joaomoreno
Copy link
Member Author

What extension are you trying to install?

@thoros1179
Copy link

I tried different extensions, such as Go, Powershell (the first two shown when browsing with ext install), but also some Angular JavaScript and TypeScript Snippets extensions. None of them can be installed.

@joaomoreno
Copy link
Member Author

Any chance I can use the same proxy you do?

@thoros1179
Copy link

I´m afraid this isn´t possible ;-) I will reconsider the issue with our proxy admin tomorrow. Maybe there is some other connection that is still blocked from our proxy. I will update you on the progress. Thank you.

@kikokikok
Copy link

Ok so now that I solved the first issue on the '#' illegal character in the declaration of the proxy + user & password url. I ended up with the 'end of central directory record signature not found' error.

I managed to track it down to the error in the DNS resolution of vortex.data.microsoft.com which is clearly blocked by our corporate proxy. for confidentiality reasons

@jithurjacob
Copy link

image

same issue in code 1.9 behind a corporate firewall with http.proxyStrictSSL set as false

@kikijhu
Copy link

kikijhu commented Mar 7, 2017

This issue stills happened on 1.10.

@jithurjacob
Copy link

Same issue in Insiders 1.11 as well

@CodeFreezr
Copy link

CodeFreezr commented Mar 28, 2017

Same issue "end of central directory record signature not found" here with:

image

Our setting for the Company-Proxy works fine with npm, Navigating the marketplace inside vscode is possible. Download via browser (IE, Chrome, Firefox) with deeper URL works, probably because of URL-Redirection. But navigating to https://vsassets.io/ brings up this error:

image

As I read it is possible to work-a-round this in the company proxy setting through ignoring this SSL-Error. But this is only a work-a-round. Can you please streamline the download URL with the SSL-Key URL so this glitch is solved at the root cause?

BTW: Perhaps it is a good Idea to offer the VSIX Link direct on the Marketplace Extension Page? Because there could be also other reasons for a seperate download flow.

@GrafRaf
Copy link

GrafRaf commented May 19, 2017

Have some error behind proxy (on try install or update packages)
image
VS code version
image

as a workaround - download packges and install offline from .vsix (as described here )

@backpacked
Copy link

backpacked commented May 19, 2017 via email

@GrafRaf
Copy link

GrafRaf commented May 19, 2017

Install v 1.12,2 and all works fine
thnx!

@abhaydhar
Copy link

Thanks ! Same issue on Corp firewall resolved with the latest update.

@rolurq
Copy link

rolurq commented Jun 28, 2017

I'm running 1.13.1, and i'm having the same bug. I'm not connecting behond a proxy. The error appears when trying to install Degugger for Chrome

@jphellemons
Copy link

jphellemons commented Jul 5, 2017

Same version as @rolurq when trying to update python 0.6.5 to 0.6.7
ps. I have no proxy configured.

@rolurq
Copy link

rolurq commented Jul 14, 2017

Updated to 1.14.0, having the same issue.

@angelia-yuqi
Copy link

updated to 1.14.2, I have the same issue. proxy setting is:
"http.proxy": "http://10.198.157.119:9400",
"http.proxyStrictSSL": false,

@bndbsh
Copy link

bndbsh commented Aug 18, 2017

This may be due to corrupt local files. I wasn't able to install certain extensions but deleting ~/.config/Code/Cache, ~/.config/Code/CachedData and ~/.config/Code/Local Storage fixed it (not sure which of the specific paths is responsible, I cleared all of them)

@komuw
Copy link

komuw commented Aug 28, 2017

@mninja thanks. that fixed it for me.

@rolurq
Copy link

rolurq commented Aug 28, 2017

upgrading to 1.15.1 fixed my issue

@AlexVFornazieri
Copy link

I'm still having this issue here, even after upgrading to version 1.15.1 :(

OS: Ubuntu 16.04 LST

Version 1.15.1
Commit 41abd21
Date 2017-08-16T17: 16: 27.618Z
Shell 1.6.6
Renderer 56.0.2924.87
Node 7.4.0
Architecture x64

@nubunto
Copy link

nubunto commented Sep 12, 2017

Having issues in 1.16 right now. No corporate proxy whatsoever.

OS: Ubuntu 16.04 LTS
Version 1.16.0
Commit 787b31c
Date 2017-09-06T16:19:37.192Z
Shell 1.7.3
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

@mninja's suggestion worked for me.

@madyasiwi
Copy link

Same issue here for some extensions on a freshly installed Ubuntu 16.04. No proxy. And unfortunately @mninja's solution does not work for me. Tried VS Code Insiders version, doesn't help. Most other extensions can be installed without problem.

extension-install-error

@kwaazaar
Copy link

Same on Windows 10, but only when I try to install the extension 'solidity' (0.0.29). Other extensions work fine. The extension itself seems to be fine as well, since nobody reported this error in that Github repo.

I'm not using proxies, whatever.

@ipsusila
Copy link

I'm also facing the same issue with newest VSCode version (1.16.1), no Proxy. I'm agree with @mninja, perhaps due to corruption of local/downloaded extension package (may be due to slow connection, behind proxy, etc...). Clearing the cache will work, or, in my case, I manually download the extension from https://marketplace.visualstudio.com/, then install the .vsix by Extensions: Install from VSIX... command.

Install from VSIX

@inuiau
Copy link

inuiau commented Sep 24, 2017

i'm having this issue too, i just download and install vscode but, when i try to install python extension i can't, but working fine for other extension
ddd

@henriquebremenkanp
Copy link

henriquebremenkanp commented Sep 25, 2017

As @mninja suggested it works.
In macOS, those folders are found inside ~/Library/Application Support/Code or ~/Library/Application Support/Code - Insiders

@ipsusila
Copy link

@inuiau My issue was exactly the same. I solved it by manually download the python extension from https://marketplace.visualstudio.com/items?itemName=donjayamanne.python, then install it from local file. See my previous comment.

@madyasiwi
Copy link

And here is the documentation on how to download extension package manually:
https://code.visualstudio.com/docs/editor/extension-gallery#_common-questions

For example:
https://donjayamanne.gallery.vsassets.io/_apis/public/gallery/publisher/donjayamanne/extension/python/0.7.0/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage

Then just rename the package extension ('VSIXPackage' in this case) to 'vsix'.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests