-
Notifications
You must be signed in to change notification settings - Fork 1
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
SSL certificate expired? Stuck on "Collecting Packages" #17
Comments
That's weird. So the SSL Certificate from ue.spdns.de (were the package repository is hosted) is valid. In October of last year some Let's Encrypt Root Certificate expired and some windows systems (mine included) did not automatically got this certificate removed and somehow try to validate certificates to the wrong certificate chain. I don't know much about it but I noticed that already in Keypirinha/Keypirinha#527. But that's not the weird part. The plugin should try the alternate repository @ https://ueffel.pythonanywhere.com/ the get the package list but that has to fail also in your case. I wonder why. Could you do the following:
After that you can solve your problem by deleting the expired certificate manually by following this: https://community.certifytheweb.com/t/upcoming-expiry-of-dst-root-ca-x3-and-r3-intermediate-for-lets-encrypt/1480/7 |
Hmm, it seems the problem is not related to Package Control, somehow something on my desktop computer. I saw the chatroom message after I posted the issue, and I was fearful that was the cause. I tried (naively) trying various methods (Powershell, certlm.msc) to identify expired certificates, when you updated the issue and pointed me to the correct way to delete the expired certificate. But that didn't work, it only changed the error message from
After UnTrusting and Disabling certs for all purposes:
|
Interesting: the ueffel.pythonanywhere.com domain seems to have the same issue, but I didn't experience that when i had the issue. Thanks for providing the debug logs. |
Was there any solution found for the |
i haven't been able to get it to work, i fear i may have to re-install |
Maybe try to update Root CAs? |
Hi what is the solution as this issue is closed? |
The solution is repair your local root certificates as there is nothing I can do on my end to fix the issue. (Because the domains have valid certificate chains) The already mentioned links:
are the only thing I have found, that help. Maybe you can share a complete stacktrace? |
This is still an issue and as far as I can tell updating root CAs doesn't work because it's an issue with Keypirinha's embedded python interpreter not updating the root CA store. So a pristine environment works fine but an older environment doesn't, even as browsers and the I'm not sure what the answer is here but it's extremely frustrating. |
The python interpreter of keypirinha does not have his own root ca store. It should always use the OS store. In my case repairing the OS store did help me instantly. |
@ueffel not sure what to tell you. openssl works. browsers work. my system python 3.10 interpreter works. my other system's keypirinha python interpreter works. it's literally just this specific application on this specific system that's broken. I should clarify that I've run through the Root CA update steps and there is nothing wrong. |
I'm having this issue too on one computer and not the other. So it's on my side but I've followed the instructions
everything executed properly, reboot, still have the issue. Do we know which certificate chain is used? So I can check the correct cert to update/remove/whatever EDIT: I've installed R3 from https://letsencrypt.org/certificates/ and it's working now |
I have the same problem - a hang on 'collecting packages'. The solution(s) presented on this page seem arcane and I had trouble at the first step. That first step - I took it from this page, which was linked above - was |
Like other issues #8 Package Control is stuck on collecting the packages.
I looked at the console, and it mentions something about the SSL certificate:
I tried reinstalling manually (copied latest release into "InstalledPackages" directory, overwriting "old" version), but the error seems to persist.
The text was updated successfully, but these errors were encountered: