-
Notifications
You must be signed in to change notification settings - Fork 39
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
error using certbot/certmanager #37
Comments
Can you give it a try with the |
The devel branch seems to have the same issue, here is what I got on the logs: Certbot:
acme2certifier:
|
Thanks for sharing the logs. I dont really see anything suspicious. Let me try to replicate the setup on my side later today. Two questions:
|
I think i found the problem. Looking into the files stored on the disk i see something strange in the
Will try to understand how this happened and how to fix it. |
I don't have the empty line between the two certificates, and nothing seems wrong within the log but I can't find the fullchain.pem/chain.pem I will keep you in touch if I manage to find any new leads, thank you ! |
I think i found the culprit. Seems certbot is quite picky with line breaks. With the above referenced fix i was able to enroll and activate a certificate with the command Give it a try and let me know how it works... |
I'm still having the same issue despite the modification. Logs are the same. |
This is strange. Which certbot version ( Will |
I have tried with both:
I found this in certbot.log:
If I copy paste the whole certificate in
|
Seems my local certbot client was too old to detect that the handler returned a pkcs#7 object instead of pem. After updating to certbot 1.5 I was able to replicate the problem. Fix 9a580fc has been pushed to devel branch which hopefully address your issue. |
It works! I have tried with both certbot and certmanager (kubernetes) and the certificate is correctly issued, thank you ! |
I successfly managed to get my certificate using acme.sh.
acme.sh --server http://myserver --register-account --accountemail [email protected] acme.sh --server http://myserver --issue -d acme-1.example.com -d example.com --standalone
But when I try using certbot or certmanager:
certbot --apache --server http://lmyserver -d example.com
I got the following error:
Error: [('asn1 encoding routines', 'ASN1_CHECK_TLEN', 'wrong tag'), ('asn1 encoding routines', 'ASN1_ITEM_EX_D2I', 'nested asn1 error'), ('asn1 encoding routines', 'ASN1_TEMPLATE_NOEXP_D2I', 'nested asn1 error'), ('PEM routines', 'PEM_ASN1_read_bio', 'ASN1 lib')]
For information, I'm using: acme2certifier and mscertsrv_ca_handler
The text was updated successfully, but these errors were encountered: