After upgrade to OPNsense 26.7.9_1 ACME client fails to validate domain.

Started by ddywz, November 16, 2026, 10:53:07 PM

Previous topic - Next topic
I updated to this new version 26.7.9_1 and noticed these errors in the acme log;   "Have replaced my domain name with "my_domain" and my API key with "my_api" in the log below.

2026-11-16T16:32:37-05:00  acme.sh [Mon Nov 16 16:32:37 EST 2026] Error adding TXT record to domain: _acme-challenge.my_domain
2026-11-16T16:32:37-05:00  acme.sh [Mon Nov 16 16:32:37 EST 2026] invalid domain
2026-11-16T16:32:37-05:00  acme.sh [Mon Nov 16 16:32:37 EST 2026] error Parameter ClientIP is missing
2026-11-16T16:32:37-05:00  acme.sh [Mon Nov 16 16:32:37 EST 2026] Parameter ClientIP is missing
2026-11-16T16:32:37-05:00  acme.sh [Mon Nov 16 16:32:37 EST 2026] error Parameter ClientIP is missing
2026-11-16T16:32:36-05:00  acme.sh [Mon Nov 16 16:32:36 EST 2026] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 7
2026-11-16T16:32:36-05:00  acme.sh [Mon Nov 16 16:32:36 EST 2026] Adding TXT value: yT0rCK_RO9lFcuRv-ERc4Y06Pb_JZFdY-T9Vg4QV1cQ for domain: _acme-challenge.my_domain
2026-11-16T16:32:36-05:00  acme.sh [Mon Nov 16 16:32:36 EST 2026] Getting webroot for domain='*.my_domain'
2026-11-16T16:32:36-05:00  acme.sh [Mon Nov 16 16:32:36 EST 2026] Getting webroot for domain='my_domain'


System log shows:

2026-11-16T16:32:38-05:00
opnsense
AcmeClient: AcmeClient: The shell command returned exit code '1': '/usr/local/sbin/acme.sh --renew --syslog 6 --log-level 1 --server 'letsencrypt_test' --dns 'dns_namecheap' --home '/var/etc/acme-client/home' --cert-home '/var/etc/acme-client/cert-home/my_api' --certpath '/var/etc/acme-client/certs/69axxxxxx7e2.852xxx6/cert.pem' --keypath '/var/etc/acme-client/keys/69adxxxxx7e2.852xxx6/private.key' --capath '/var/etc/acme-client/certs/69axxxxxx7e2.852xxxxx6/chain.pem' --fullchainpath '/var/etc/acme-client/certs/69axxxxxx7e2.852xxxxx6/fullchain.pem' --domain 'my_domain' --domain '*.my_domain' --days '60' --keylength '4096' --accountconf '/var/etc/acme-client/accounts/69axxxxxx7e2.852xxxxx6_stg/account.conf''


I tried to renew manually but same error.   Anyone has seen this error? There have been no other changes.  I opened a ticket with Namecheap to check on DNS and API but they look fine.

It appears during the renew process it fails to add the TXT record in the DNS and fails validation.   

I was able to fix this, but don't know why it happened. First I updated to 26.7.9_3 last night and attempted another renewal which failed with same domain validation error, but instead of calling for "Parameter ClientIP missing"  it said "API Key is invalid or API access has not been enabled".  I switched the server to letsencrypt-testing and issued a renewal via CLI

[Tue Nov 17 09:49:32 EST 2026] Adding TXT value: XypHXZwhKSSND0AUkPCCMi8aq7ZSQ_Hcw6LTOIJH0Mw for domain: _acme-challenge.my_domain
[Tue Nov 17 09:49:33 EST 2026] error API Key is invalid or API access has not been enabled
[Tue Nov 17 09:49:33 EST 2026] API Key is invalid or API access has not been enabled
[Tue Nov 17 09:49:34 EST 2026] error API Key is invalid or API access has not been enabled
[Tue Nov 17 09:49:34 EST 2026] invalid domain

Made sure that the API key showed correct and saved under
Services: ACME Client: Challenge Types

I went on cli and checked

/var/etc/acme-client/accounts/69axxxxxxxxxxxxx_stg/account.conf  file, and the API key there did not match with what I updated in the GUI.
Manually did a vi and updated the file with correct API and saved it.  Ran another renewal manually from CLI and now it worked fine and renewed the cert.
Switched server to production under ACME client --> accounts and issued a renew from the production server letsencrypt(default) and all worked fine.

Questions;
1. is there supposed to be only one account.conf file under this *_stg directory?  Is there an account for production sever?
2. How come the API key on account.conf was totally different from what I set it up?
3. How was this working before?

Could the upgrade to 26.7.9 caused this?
Since editing account.conf to the correct Namecheap key fixed DNS validation, that file was the effective credential source for that run.