Unable To Renew Certs Since last ACME package Update

costanzo

I have the same issue.

costanzo

FYI - I created a support ticket. Request ID [#INC-50562]. Let me know if you need any logs, or other information that would help.

Thanks in advance.

stephenw10

Ok we see that and are investigating.

Yes, please add any logs you have on the ticket.

Steve

costanzo

@stephenw10
Done - uploaded the error, log detail as well as info on my DNS and API Token setup from CloudFlare.

Thanks again for your help.

yuljk

@stephenw10 Thanks for looking into this. Much appreciated.

raiderj

I think I'm having the same issue. In addition to the error text shown earlier, I have what I think is a related error further up the in the acme_issuecert.log

[Wed Apr 29 03:16:05 EDT 2020] response='{"success":false,"errors":[{"code":0,"message":"Actor 'com.cloudflare.api.token.<api_token_that_I_created>' requires permission 'com.cloudflare.api.account.zone.list' to list zones"}],"messages":[],"result":null}'
  "token": "<another_token_here>"

I gave one API token a Zone.Zone and Zone.DNS edit rights, which I then pasted in pfsense during the ACME configuration using Cloudflare as my DNS.

stephenw10

Yes, we see the issue and are working on an update to fix it.

Steve

costanzo

@raiderj

I think thy are working to have a fix soon. In the meantime, here's a workaround:

Use Manual DNS

Create a TXT record in your Cloudflare DNS

Change the dropdown to Manual DNS

Save
Click Issue
Copy the _acme-challenge key (you will see this displayed after hitting issue)
Go in to your DNS and update the key in the TXT record
Wait for 2-3 Minutes (this is to give time for the DNS record to propagate)
Go back in to the Acme and click Renew

raiderj

@costanzo

Thank you! That worked perfectly. Pasted part of the log below. I do have a question - would this also work for wildcard domains? That's at least what I'm trying to do with my setup. I just have a single entry in my Domain SAN list for the wildcard domain.

Successful Result:

[Wed Apr 29 12:38:58 EDT 2020] Single domain='*.subdomain.domain.com'
[Wed Apr 29 12:38:58 EDT 2020] Getting domain auth token for each domain
[Wed Apr 29 12:38:58 EDT 2020] Verifying: *.subdomain.domain.com
[Wed Apr 29 12:39:02 EDT 2020] Success
[Wed Apr 29 12:39:02 EDT 2020] Verify finished, start to sign.
[Wed Apr 29 12:39:02 EDT 2020] Lets finalize the order, Le_OrderFinalize: https://acme-staging-v02.api.letsencrypt.org/acme/finalize/13385284/...
[Wed Apr 29 12:39:03 EDT 2020] Download cert, Le_LinkCert: https://acme-staging-v02.api.letsencrypt.org/acme/cert/fa7e...
[Wed Apr 29 12:39:03 EDT 2020] Cert success.

costanzo

@raiderj

Yes. You need to create two SANs: one for the example.com and one for *.example.com

It probable doesn't mater, but I would list the example.com domain first.

For example:

Also, make sure you your domain listed in your Cloudflare DNS record too. Eg, have example.com.

raiderj

@costanzo
Updated my configs. Working still with both SANs being list, and I also see the resulting certs in the filesystem for both my wildcard and standard domains.
I didn't test it extensively, but the order of the SAN list doesn't seem to matter. I did leave the wildcard listing last as you recommended.

raiderj

Switched over to a production setup, and there seems to be an issue. When I first go to issue, there's two TXT values that are being asked to enter into Cloudflare. One for the wildcard cert, one for the regular cert. But they're both looking for the same key value (_acme-challenge.subdomain.domain.com).
Right now I'm able to get the wildcard cert to return, but not the normal cert. Maybe manual-DNS doesn't work for wildcard certs in Production?

jimp

Update the ACME package and try again, there was a change to the CloudFlare script in the ACME.sh repo which is in the new version. Worth a try.

cakewalk

@jimp Thanks for the quick turn around! Confirmed fixed for me.

bartkowski

I'm seeing another issue, not sure if related to this. I'm using DNS-Hurricane Electric method.
I think the referrer should be my external IP, but also when I query my FQDN of my pfsense box, it returns 192.168.2.1, so is it a DNS issue?

2020/04/29 13:27:18 [error] 44990#100120: *3720 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.168.2.25, server: , request: "POST /acme/acme_certificates.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.2.1", referrer: "https://192.168.2.1/acme/acme_certificates.php"

jimp

@bartkowski Start a new thread for that. This one is only for CloudFlare. And make sure you have updated to the new ACME package (just put up an hour or two ago)

raiderj

@jimp
Updated to the latest package, but wildcard certs aren't coming down for my domain. Normal cert is coming in, properly signed with the Prod Let's Encrypt CA. Maybe because the second domain in the SAN list is the wildcard listing?

EDIT: Yes, if I switch the SAN order to the wildcard first, it comes down. With this workaround using DNS-Manual, should I switch back to the DNS-Cloudflare option? Maybe the new ACME package fixes this?

jimp

If that's also on CloudFlare it may be a different issue.

The one the update had a fix for is https://github.com/acmesh-official/acme.sh/issues/2888

costanzo

@raiderj said in Unable To Renew Certs Since last ACME package Update:

One for the wildcard cert, one for the regular cert. But they're both looking for the same key valu

Odd. Can you post a screen capture of the message show when issuing the cert. Be sure to blur out any sensitive data. I am not seeing this issue, but may be different for you.

Also, keep in mind generating too many certs under production will cap you out and you will need to wait a week. Best to use the staging option.

raiderj

@costanzo said in Unable To Renew Certs Since last ACME package Update:

@raiderj said in Unable To Renew Certs Since last ACME package Update:

One for the wildcard cert, one for the regular cert. But they're both looking for the same key valu

Odd. Can you post a screen capture of the message show when issuing the cert. Be sure to blur out any sensitive data. I am not seeing this issue, but may be different for you.

Also, keep in mind generating too many certs under production will cap you out and you will need to wait a week. Best to use the staging option.

I'll do that if I see it again. I can't replicate the issue at the moment. The only issue I have now, with both staging and production is that the second domain in the SAN list won't get an updated cert. Haven't tried switching to the DNS-Cloudflare option though.