Originally created by @wibimaster on GitHub (Sep 17, 2016).
Hi,
I try to create a certificate with DNS validation, but it always fail on fullchain creation :
```
+ Challenge is valid!
+ Requesting certificate...
+ Checking certificate...
+ Done!
+ Creating fullchain.pem...
unable to load certificate
140288499504896:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:crypto/asn1/asn1_lib.c:100:
```
I take a look on the code, and after some debug I see that the certificate that fail comes from :
http://cert.int-x3.letsencrypt.org/
Note: I'm working with "OpenSSL 1.1.0 25 Aug 2016"
I tried :
```
wget -4 http://cert.int-x3.letsencrypt.org/ && \
mv index.html test.pem && \
openssl x509 -in "test.pem" -inform DER -out "test2.pem" -outform PEM
```
=> fail
```
wget -4 http://cert.int-x3.letsencrypt.org/ && \
mv index.html test.pem && \
openssl x509 -in "test.pem" -inform DER -out "test2.pem" -outform PEM
```
=> success
The only difference is the name of the output file which is different from the input file.
On your bash script you do the same thing :
```
openssl x509 -in "${CERTDIR}/${domain}/chain-${timestamp}.pem" -inform DER -out "${CERTDIR}/${domain}/chain-${timestamp}.pem" -outform PEM
```
I try a rename before :
```
mv ${CERTDIR}/${domain}/chain-${timestamp}.pem ${CERTDIR}/${domain}/tmp-chain-${timestamp}.pem
openssl x509 -in "${CERTDIR}/${domain}/tmp-chain-${timestamp}.pem" -inform DER -out "${CERTDIR}/${domain}/chain-${timestamp}.pem" -outform PEM
```
and it works.
Can you fix it ?
Thanks !
adam
added the bug label 2025-12-29 00:25:50 +01:00
All seems good but DNS validation is very slow, I could validate as soon as it's finished
@wibimaster commented on GitHub (Sep 17, 2016):
I got a fail now, don't know if it's a consequence of the fix :
```
Processing xxx.xxx with alternative names: www.xxx.xxx
+ Signing domains...
+ Creating new directory /home/xxx/dehydrated/certs/xxx.xxx ...
+ Generating private key...
+ Generating signing request...
+ Requesting challenge for xxx.xxx...
+ ERROR: An error occurred while sending post-request to https://acme-staging.api.letsencrypt.org/acme/new-authz (Status 403)
Details:
{
"type": "urn:acme:error:unauthorized",
"detail": "No registration exists matching provided key",
"status": 403
}
```
**EDIT**
Sorry, just see https://github.com/lukas2511/dehydrated/issues/92
All seems good but DNS validation is very slow, I could validate as soon as it's finished
@wibimaster Since you are doing dns validation the temporary error was probably because the dns entry didn't propagate fast enough.
@lukas2511 commented on GitHub (Sep 17, 2016):
@wibimaster Since you are doing dns validation the temporary error was probably because the dns entry didn't propagate fast enough.
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 @wibimaster on GitHub (Sep 17, 2016).
Hi,
I try to create a certificate with DNS validation, but it always fail on fullchain creation :
I take a look on the code, and after some debug I see that the certificate that fail comes from :
http://cert.int-x3.letsencrypt.org/
Note: I'm working with "OpenSSL 1.1.0 25 Aug 2016"
I tried :
=> fail
=> success
The only difference is the name of the output file which is different from the input file.
On your bash script you do the same thing :
I try a rename before :
and it works.
Can you fix it ?
Thanks !
@lukas2511 commented on GitHub (Sep 17, 2016):
@wibimaster can you check if that fixed your problem?
@wibimaster commented on GitHub (Sep 17, 2016):
I got a fail now, don't know if it's a consequence of the fix :
EDIT
Sorry, just see https://github.com/lukas2511/dehydrated/issues/92
All seems good but DNS validation is very slow, I could validate as soon as it's finished
@wibimaster commented on GitHub (Sep 17, 2016):
That's OK, temporary got a fail :
But after a retry all seems good :)
Thanks !
@lukas2511 commented on GitHub (Sep 17, 2016):
@wibimaster Since you are doing dns validation the temporary error was probably because the dns entry didn't propagate fast enough.