su - alta -c 'cd /usr/share/access/be && ./uacme.sh'
uacme: version 1.7.1 starting on Mon, 06 Jul 2026 21:50:36 +0000
uacme: loading key from /var/lib/access/certs/[redacted]/private/key.pem
uacme: loading key from /var/lib/access/certs/[redacted]/private/[redacted].ddns.manage.alta.inc/key.pem
uacme: checking existence and expiration of /var/lib/access/certs/[redacted]/[redacted].ddns.manage.alta.inc/cert.pem
uacme: /var/lib/access/certs/[redacted]/[redacted].ddns.manage.alta.inc/cert.pem expires in -4 days
uacme: /var/lib/access/certs/[redacted]/[redacted].ddns.manage.alta.inc/cert.pem is due for renewal
uacme: generating certificate request
uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory
uacme: retrieving account at https://acme-v02.api.letsencrypt.org/acme/new-acct
uacme: account location: https://acme-v02.api.letsencrypt.org/acme/acct/[redacted]
uacme: creating new order at https://acme-v02.api.letsencrypt.org/acme/new-order
uacme: failed to create new order at https://acme-v02.api.letsencrypt.org/acme/new-order
uacme: the server reported the following error:
{
"type": "urn:ietf:params:acme:error:rateLimited",
"detail": "too many certificates (5) already issued for this exact set of identifiers in the last 168h0m0s, retry after 2026-07-07 11:12:06 UTC: see https://letsencrypt.org/docs/rate-limits/#new-certificates-per-exact-set-of-identifiers",
"status": 429
}
As my controller cannot renew the Let’s Encrypt cert, I’m unable to control my APs, which is not that great…
Is this the intended behavior and if so that’s a little bit unfortunate. I have not seen anyone else run into this issue here on the forum.
((I am running the self-hosted version as a LXC container on Proxmox. There might have been some issues with storage space because of growing log files in the container, which could have caused this.)