-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
Comments
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. |
@maritz Just to confirm, did you try this build? |
I'm also behind corporate proxy with authentication. It works at home, but no luck with installing any extensions on work PC. |
@joaomoreno I have not. I would need a linux x64 build to test it, though. |
+1 same here. "end of central directory record signature not found" Version 0.10.6 |
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. |
It's working on 0.10.7-insider |
Excellent news. @takuan-osho @JFLavidalle @vilinski, maybe you guys can let us know if the issue's fixed for you as well? |
still no version update this week? |
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/ |
@joaomoreno : I can confirm that the issue is fixed for me on release 0.10.7-insider. |
OK, got confirmation from 2 people that it is fixed, so closing this. Thanks! |
confirm working with stable and insiders builds. Finally can install extensions |
For me the issue is NOT fixed. I tried 0.10.8 and 0.10.8 Insider. |
@thoros1179 Did you configure the |
What extension are you trying to install? |
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. |
Any chance I can use the same proxy you do? |
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. |
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 |
This issue stills happened on 1.10. |
Same issue in Insiders 1.11 as well |
Same issue "end of central directory record signature not found" here with: 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: 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. |
Have some error behind proxy (on try install or update packages) as a workaround - download packges and install offline from .vsix (as described here ) |
I got the latest 1.12.x and the proxy works without flaw, even when using AD authentication. I can download the extensions without any issues now.
Good job!
… On May 18, 2017, at 9:13 PM, Rafael ***@***.***> wrote:
Have some error behind proxy (on try install or update packages)
VS code version
as a workaround - download packges and install offline from .vsix (as described here )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Install v 1.12,2 and all works fine |
Thanks ! Same issue on Corp firewall resolved with the latest update. |
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 |
Same version as @rolurq when trying to update python 0.6.5 to 0.6.7 |
Updated to 1.14.0, having the same issue. |
updated to 1.14.2, I have the same issue. proxy setting is: |
This may be due to corrupt local files. I wasn't able to install certain extensions but deleting |
@mninja thanks. that fixed it for me. |
upgrading to 1.15.1 fixed my issue |
I'm still having this issue here, even after upgrading to version 1.15.1 :( OS: Ubuntu 16.04 LST Version 1.15.1 |
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 |
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. |
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 |
As @mninja suggested it works. |
@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. |
And here is the documentation on how to download extension package manually: Then just rename the package extension ('VSIXPackage' in this case) to 'vsix'. |
Related to #69
@joaomoreno
@takuan-osho
@vilinski
@JFLavidalle
Ping @maritz
The text was updated successfully, but these errors were encountered: