Originally created by @taylorotwell on GitHub (Jul 18, 2017).
Starting today, all our customers have started receiving this error when issuing certificates using deydrated:
# INFO: Using main config file /root/letsencrypt1500328841/config
./dehydrated: line 415: CA_REVOKE_CERT: unbound variable
Originally created by @taylorotwell on GitHub (Jul 18, 2017).
Starting today, all our customers have started receiving this error when issuing certificates using deydrated:
```
# INFO: Using main config file /root/letsencrypt1500328841/config
./dehydrated: line 415: CA_REVOKE_CERT: unbound variable
```
So I guess there's something more to it.
I figured it out, you'll need to update your code to the latest version first. Then you can apply the patch.
C/
@csandescu commented on GitHub (Jul 18, 2017):
You can easily fix that by using lazy evaluation in bash like this:
`if [[ "${statuscode}" = "409" ]] && [[ "${2}" = "${CA_REVOKE_CERT}" ]]; then`
However, after fixing it I'm getting:
> + ERROR: An error occurred while sending post-request to https://acme-v01.api.letsencrypt.org/acme/new-cert (Status 500)
>
> Details:
> {
> "type": "urn:acme:error:serverInternal",
> "detail": "Error creating new cert",
> "status": 500
> }
So I guess there's something more to it.
I figured it out, you'll need to update your code to the latest version first. Then you can apply the patch.
C/
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 @taylorotwell on GitHub (Jul 18, 2017).
Starting today, all our customers have started receiving this error when issuing certificates using deydrated:
@csandescu commented on GitHub (Jul 18, 2017):
You can easily fix that by using lazy evaluation in bash like this:
if [[ "${statuscode}" = "409" ]] && [[ "${2}" = "${CA_REVOKE_CERT}" ]]; thenHowever, after fixing it I'm getting:
So I guess there's something more to it.
I figured it out, you'll need to update your code to the latest version first. Then you can apply the patch.
C/
@lukas2511 commented on GitHub (Jul 18, 2017):
@taylorotwell can you please test with the newest version? this should be fixed now