Originally created by @Eihrister on GitHub (Mar 29, 2018).
Hi!
For some reason, when issuing my wildcard certificate (ACMEv2), it appears fullchain.pem ends up with the same intermediary certificate (chain.pem) twice.
I notice ^M line -endings in the first iteration of the intermediary in fullchain.pem, which do not exist in the chain.pem. However, upon opening cert.pem, it seems the intermediary is already there, with the ^M line-endings.
I suspect that with ACMEv2, the contents of chain.pem already comes from Let's Encrypt (hence being stored in cert.pem).
Daniël
Originally created by @Eihrister on GitHub (Mar 29, 2018).
Hi!
For some reason, when issuing my wildcard certificate (ACMEv2), it appears fullchain.pem ends up with the same intermediary certificate (chain.pem) twice.
I notice ^M line -endings in the first iteration of the intermediary in fullchain.pem, which do not exist in the chain.pem. However, upon opening cert.pem, it seems the intermediary is already there, with the ^M line-endings.
I suspect that with ACMEv2, the contents of chain.pem already comes from Let's Encrypt (hence being stored in cert.pem).
Daniël
Yeah, Lukas just showed me on IRC as well. I was using 0.6.1, cloned the repo to make a fix, then tested with the same 0.6.1 release on a different machine that had my hook scripts. I need more caffeine.
@Eihrister commented on GitHub (Mar 29, 2018):
Yeah, Lukas just showed me on IRC as well. I was using 0.6.1, cloned the repo to make a fix, then tested with the same 0.6.1 release on a different machine that had my hook scripts. I need more caffeine.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Eihrister on GitHub (Mar 29, 2018).
Hi!
For some reason, when issuing my wildcard certificate (ACMEv2), it appears fullchain.pem ends up with the same intermediary certificate (chain.pem) twice.
I notice ^M line -endings in the first iteration of the intermediary in fullchain.pem, which do not exist in the chain.pem. However, upon opening cert.pem, it seems the intermediary is already there, with the ^M line-endings.
I suspect that with ACMEv2, the contents of chain.pem already comes from Let's Encrypt (hence being stored in cert.pem).
Daniël
@txr13 commented on GitHub (Mar 29, 2018):
Please check your dehydrated version. This should be fixed in master a while back.
@Eihrister commented on GitHub (Mar 29, 2018):
Yeah, Lukas just showed me on IRC as well. I was using 0.6.1, cloned the repo to make a fix, then tested with the same 0.6.1 release on a different machine that had my hook scripts. I need more caffeine.