Re: Certificate renewal fails after upgrade to httpd v2.4.66

Rich Bowen <[email protected]> Fri, 19 Jun 2026 08:14:57 -0400
Newsgroups gmane.comp.apache.user
Message-ID <[email protected]>
As Deepak says, the =E2=80=9913=E2=80=99 in that error message almost =
always refers to a filesystem permission problem. Check the files and =
the directory tree in which it lives for correct read/write permissions. =
Consider turning up the logging level if that doesn=E2=80=99t help.

> On Jun 19, 2026, at 7:54=E2=80=AFAM, Abfalterer, Armin =
<[email protected]> wrote:
>=20
> The error status urn:ietf:params:acme:error:unauthorized seems to come =
from the CA Provider so I deem that it is not a local permission issue.
> Von: Deepak Goel <[email protected]>
> Gesendet: Freitag, 19. Juni 2026 12:16
> An: [email protected] <[email protected]>
> Betreff: Re: [users@httpd] Certificate renewal fails after upgrade to =
httpd v2.4.66
>  Sie erhalten nicht h=C3=A4ufig E-Mails von [email protected]. =
Erfahren Sie, warum dies wichtig ist
> looks like a directory or file access issue=20
>=20
>    "status-description": "Permission denied",
>=20
> You might have to check with ls -lt command and then do a chmod
>=20
>=20
>=20
>=20
> Deepak
> "The greatness of a nation can be judged by the way its animals are =
treated - Mahatma Gandhi"
>=20
> +91 73500 12833
> [email protected]
>=20
> LinkedIn: www.linkedin.com/in/deicool
>=20
> "Plant a Tree, Go Green"
>=20
> Make In India : http://www.makeinindia.com/home
>=20
>=20
> On Fri, Jun 19, 2026 at 3:43=E2=80=AFPM Abfalterer, Armin =
<[email protected]> wrote:
> Hi all
> An instance running httpd v2.4.66 persistently fails to renew =
certificates with an ACME unauthorized error. ZeroSSL rejects the =
replaces field in the new order, claiming the certificate being replaced =
does not belong to the current ACME account. Renewal never succeeds and =
the error counter keeps incrementing.
> Renewal was working prior to the upgrade to v2.4.66.
> Environment
>     =E2=80=A2 Apache httpd version: 2.4.66
>     =E2=80=A2 ACME CA: ZeroSSL
> Observed Behavior
> Renewal fails repeatedly with error count accumulating. The job.json / =
md-status output shows status 13 (Permission denied), problem =
urn:ietf:params:acme:error:unauthorized, with the detail: "The =
'replaces' field does not identify a certificate that belongs to this =
ACME account", during the activity "Creating new order ... =
replacing-cert=3D...".
>=20
> {
>   "renewal": {
>     "name": "xxx",
>     "finished": false,
>     "notified": false,
>     "notified-renewed": false,
>     "next-run": "Fri, 19 Jun 2026 06:09:00 GMT",
>     "last-run": "Thu, 18 Jun 2026 22:44:59 GMT",
>     "errors": 11,
>     "last": {
>       "status": 13,
>       "status-description": "Permission denied",
>       "problem": "urn:ietf:params:acme:error:unauthorized",
>       "detail": "The \"replaces\" field does not identify a =
certificate that belongs to this ACME account",
>       "activity": "Creating new order, key-spec=3Ddefault, =
profile=3Dnone, replacing-cert=3Dxxx"
>     },
>     "cert": {}
>   }
> }
>=20
> Is this a known issue? Is there a recommended mitigation?
>=20
> Regards, Armin