-
Notifications
You must be signed in to change notification settings - Fork 824
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
Fullchain.pem expired / force renewal doesn't renew #881
Comments
Hi, isn't this caused by the DST Root CA X3 expiration ? |
I have the same issue and still could not figure out if it is related to this project or not. |
@gurumark @fluffyst |
Didn't fix it for me at least. I've got the same phenomenon, that cert_status shows all fullchains as expired ( It doesn't seem to make a difference if I use |
Did someone find the fix for this? I'm facing the same issue with the fullchain.pem file |
The only way to show the fullchain as OK instead of expired is to manually edit the fullchain.pem and remove the last cert in the chain. |
Just to clarify: the I know the preferred chain stuff has been an issue on the acme.sh side for a while, the more recent version 3.x might finally solve this but I'll have to check a few things before bumping to this version. It's fairly easy to locally build an acme-companion image with a different version of acme.sh, I can provide instructions for this if needed. |
Since one year I'm running a mailcow-dockerized behind nginx-proxy. |
I think that is so. I've created an issue on the Let's Encrypt forum. Follow the link to find the suggested solution. I tried to find a solution myself, and the following is probably not needed anymore, but just in case, to extract the first certificate from a file:
|
So, just recently i've been getting curl certificate expired errors on my ubuntu 14.04 server, however it works just fine on any other server, including my local machine
curl: (60) SSL certificate problem: certificate has expired
A bit of investigating, I believe that the Intermediate has expired or is invalid, whynopadlock result shows that, along with
/app/cert_status
command showing that the fullchain.pem has expired, force renewing doesn't seem to fix the issue, it 100% renews the certificate however.Info: running acme-companion version v2.1.0-28-g1785bc5
rendered nginx configuration
The text was updated successfully, but these errors were encountered: