-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
The certificate of 'packages.sury.org' has expired. #1729
Comments
Got the same issue, found it yesterday, Docker with ubuntu 20.4 in WSL2 |
What's output of: |
I see following:
|
|
@oerdnj I don't know if you change something but it started to work
|
Nope, haven't touched a thing. |
It's weird. The certificate only works with |
I guess you are missing |
FWIW, that Your Dockerfile should've stopped already there.
|
I don't see a problem on the server, closing the issue. |
I found case. I used |
I face the same problem. lsb_release -a > No LSB modules are available. gnutls-cli packages.sury.org:443 > Processed` 127 CA certificate(s).
|
@akaPipo Your system is out of date or misconfigured and that's the problem. A current system/browser shows a valid cert. |
Thanks for your reply. Still can't find a reason. This repo was added years ago and worked well like a charm. I have already done apt-get upgrade && apt-get update. By the way, other non-debian (not official) repos works well, there is no such error. |
I should note that Debian stretch goes out of support in 15 days :( So you have more work to do than just resolving this. |
Yep, as documented here: #1785 I'll do one last update and send newsletter to the Patreon and GitHub Sponsors and then Debian stretch repositories will be decommissioned. |
I have finally fixed it! The issue was the DST Root CA X3 cross-sign has expired To fix it on debian:
found on Stackoverflow |
resolvi com isto |
Describe the bug
Add sury gpg key return that certificate is expired
To Reproduce
Expected behavior
Cert should be added
Distribution (please complete the following information):
The text was updated successfully, but these errors were encountered: