-
Notifications
You must be signed in to change notification settings - Fork 27
Renovate image appears to include expired CA for Let's Encrypt certificates #235
Comments
Which version of the image are you using? |
@rarkins seeing this too now at my bot. 😱 Node is working fine, but git checkout fails. Will try to fix later today. 😕 |
https://community.letsencrypt.org/t/production-chain-changes/150739 But I still don't understand why we're affected. Neither Ubuntu or git are old |
Current image on my install is: No pending updates from upstream (per Renovate itself anyway :) ) |
@viceice can we add this?
|
The issue should be fixed with next base image update in next two or three hours. Maybe you need to manually update to latest docker digest. |
Latest images are working again |
Confirmed working with the latest 0.27.25 image on my infrastructure. Thank you for your extremely fast response and diligent work to fix this! |
Special thanks to @viceice for fixing it late at night while on vacation! |
Context on CA expiration: https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/
The
renovate/renovate
image, as used by a renovate-runner instance in our local Gitlab installation, is currently experiencing errors like this when accessing any repository, starting at ~9AM CDT 9/30/2021:Our Gitlab installation uses a Let's Encrypt issued certificate, rooted in the new "ISRG Root X1" CA that is valid until 2035. Our current server cert is valid until 29 Nov 2021. Inspecting this cert in an up-to-date browser (both Chrome and Firefox) shows a valid certificate and trust chain.
This leads me to conclude that the trusted CAs inside the
renovate/renovate
image need to update to include an updated list of trusted CAs, including the newer ISRG Root X1 root CA.The text was updated successfully, but these errors were encountered: