openwrt / openwrt/packages

uacme: dns-api broken

Open
#29,567 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Package Name

uacme

Maintainer

@orangepizza

OpenWrt Version

SNAPSHOT

OpenWrt Target/Subtarget

bcm27xx/bcm2711

Steps to Reproduce
/usr/sbin/uacme -v -t EC --bits 384 --days 15 -h /usr/lib/acme/client/dnschalhook.sh --confdir /etc/acme issue office.example.com my.example.com office.example.org
uacme: version 1.8.1 starting on Wed, 27 May 2026 09:10:06 -0400
uacme: loading key from /etc/acme/private/key.pem
uacme: created directory /etc/acme/office.example.com/
uacme: loading key from /etc/acme/private/office.example.com/key.pem
uacme: /etc/acme/private/office.example.com/key.pem not found
uacme: generating new 384-bit EC key
uacme: key saved to /etc/acme/private/office.example.com/key.pem
uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory
uacme: checking existence and expiration of /etc/acme/office.example.com/cert.pem
uacme: /etc/acme/office.example.com/cert.pem does not exist
uacme: generating certificate request
uacme: retrieving account at https://acme-v02.api.letsencrypt.org/acme/new-acct
uacme: no account associated with /etc/acme/private/key.pem found at https://acme-v02.api.letsencrypt.org/acme/new-acct. Consider trying 'new'

ok so I try this:

uacme -v -c /etc/acme/private new
uacme: version 1.8.1 starting on Wed, 27 May 2026 09:06:27 -0400
uacme: created directory /etc/acme/private/private
uacme: loading key from /etc/acme/private/private/key.pem
uacme: /etc/acme/private/private/key.pem not found
uacme: generating new 2048-bit RSA key
uacme: key saved to /etc/acme/private/private/key.pem
uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory
uacme: creating new account at https://acme-v02.api.letsencrypt.org/acme/new-acct
uacme: type 'y' to accept the terms at https://letsencrypt.org/documents/LE-SA-v1.6-August-18-2025.pdf
y
uacme: account created at https://acme-v02.api.letsencrypt.org/acme/acct/3375974116

That still doesn't help.

Actual Behaviour

uacme dns-api via cloudflare does not appear to be working.

Wiping and trying to recreate the /etc/acme folder doesn't help either.

Confirmation Checklist

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the documented uacme command on OpenWrt with /usr/lib/acme/client/dnschalhook.sh and the listed /etc/acme paths. Trace the account setup and DNS challenge flow, then verify that the Cloudflare-backed dns-api works end to end for the example domains.

Written by the indexing model from the issue text.

Assessment

Domain
api, cli, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.