ACME DNS-Authenticators with OVH

TrueNAS General
,
1

Godo morning all,

My account here has been reset due to SSO with Google (didn’t connect my previous account).

I just installed on a new machine Truenas Scale 25.04.1 community edition and I just can’t

  1. Have the ACME DNS-Authenticators with OVH working (API has been properly been set and root has an email configured)
  2. Manage to use the API to create a certificate using a script inside a custom app.

curl -k -v -X POST “https://${TRUENAS_HOST}/api/v2.0/certificate”
-H “Authorization: Bearer $TRUENAS_API_KEY”
-H “Content-Type: application/json”
-d “$(jq -n
–arg name “$CERT_NAME”
–arg cert “$(cat nas.teeptrak.com.cer)”
–arg key “$(sudo cat nas.teeptrak.com.key)”
‘{
create_type: “CERTIFICATE_IMPORTED”,
name: $name,
certificate: $cert,
privatekey: $key
}’)”

This is driving me nuts.
I need to have Letsencrypt certificate renewed wih DNS acme challenge as my NAS is not directly open to the outside world.

Any hints?
Is the DNS authenticator with OVH broken?
When I launch “Create ACME Certificate”, I get a windows that shows for less than 1 seconds and the UI get stuck.

Thank all!

2

No, all ACME cert issuance (or more precisely, ACME account creation) is broken. It’s said to be fixed in 25.04.2, due out this week. Or, as a workaround:

1 Like
3

job certificate create has failed many times

[
{
"name": "letsencrypt",
"csr_id": 5,
"tos": true,
"create_type": "CERTIFICATE_CREATE_ACME",
"renew_days": 10,
"acme_directory_uri": "letsencrypt url",
"dns_mapping": {
"nas.teeptrak.com": 5,
"DNS:nas.teeptrak.com": 5
}
}
]

I can’t find more information… Thank you

4

Thank you… Half a day lost :disappointed_relieved: