Originally created by @lukavia on GitHub (May 8, 2018).
I've discovered that after installing the latest version my .pem files started to contain diffrent data:
cert-xxxx...pem - contains the certificate and the chain
chain-xxxx...pem - contains the chain and a link above http://cert.int-x3.letsencrypt.org/
fullchain-xxxx...pem - contains the combination of the above. That is: the cert, the chain, the link, and the chain again.
Originally created by @lukavia on GitHub (May 8, 2018).
I've discovered that after installing the latest version my .pem files started to contain diffrent data:
cert-xxxx...pem - contains the certificate and the chain
chain-xxxx...pem - contains the chain and a link above http://cert.int-x3.letsencrypt.org/
fullchain-xxxx...pem - contains the combination of the above. That is: the cert, the chain, the link, and the chain again.
@lukavia You’re not using the latest version. Please upgrade—a fix for this has already been implemented. (Specifically, in 0.6.2.)
@txr13 commented on GitHub (May 8, 2018):
@lukavia You’re not using the latest version. Please upgrade—a fix for this has already been implemented. (Specifically, in 0.6.2.)
@lukavia commented on GitHub (May 9, 2018):
Since I install from debian packages I've posted a bug with them to upgrade the version https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898254
In Debian, 0.6.1-2 contains the fix (that I uploaded several days before 0.6.2 was released). Most likely you obtained that certificate with 0.6.1-1 but noticed only now.
Make sure you have installed the latest updates (which means 0.6.1-2~bpo9+1) and try re-issuing the certificate.
@mapreri commented on GitHub (May 9, 2018):
In Debian, 0.6.1-2 contains the fix (that I uploaded several days before 0.6.2 was released). Most likely you obtained that certificate with 0.6.1-1 but noticed only now.
Make sure you have installed the latest updates (which means `0.6.1-2~bpo9+1`) and try re-issuing the certificate.
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 @lukavia on GitHub (May 8, 2018).
I've discovered that after installing the latest version my .pem files started to contain diffrent data:
cert-xxxx...pem - contains the certificate and the chain
chain-xxxx...pem - contains the chain and a link above http://cert.int-x3.letsencrypt.org/
fullchain-xxxx...pem - contains the combination of the above. That is: the cert, the chain, the link, and the chain again.
@txr13 commented on GitHub (May 8, 2018):
Please run “dehydrated -v” and post the resulting output.
@lukavia commented on GitHub (May 8, 2018):
@txr13 commented on GitHub (May 8, 2018):
@lukavia You’re not using the latest version. Please upgrade—a fix for this has already been implemented. (Specifically, in 0.6.2.)
@lukavia commented on GitHub (May 9, 2018):
Since I install from debian packages I've posted a bug with them to upgrade the version https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898254
@mapreri commented on GitHub (May 9, 2018):
In Debian, 0.6.1-2 contains the fix (that I uploaded several days before 0.6.2 was released). Most likely you obtained that certificate with 0.6.1-1 but noticed only now.
Make sure you have installed the latest updates (which means
0.6.1-2~bpo9+1) and try re-issuing the certificate.@lukavia commented on GitHub (May 9, 2018):
I confirm that this is fixed in 0.6.1-2