[SOLVED] Issue with Proxmox 8.2 Namecheap ACME DNS Plugin.

[reub]

Hi - I'm running Proxmox 8.2.2 and running into the following odd error trying to provision certificates using the Namecheap ACME DNS Plugin. I believe this same configuration worked prior to the 8.2 upgrade within the last monthacme

1. Under Datacenter -> ACME, I've defined a challenge plugin using:
   1. Plugin ID: namecheap
   2. Validation Delay: 30 (default)
   3. DNS API: namecheap
   4. API Data:
      1. export NAMECHEAP_USERNAME="<username>"
         export NAMECHEAP_API_KEY="<validapikey>"
         export NAMECHEAP_SOURCEIP="<validsourceip>"
2. I validated that the username, api key and source ip work using the namecheap api directly using curl.
3. Under <node> -> System -> Certificates, I've defined a domain using:
   1. Challenge Type: DNS
   2. Plugin: namecheap
   3. Domain: <FQDN of node>
4. When I click "Order Certificates Now", I get an error with the following message implying that the API Data values are not being passed as expected (or that the API KEY itself is not being specified by the command):

Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/<redacted>/<redacted>
Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/<redacted>'
The validation for <FQDN of node> is pending!
[Fri May  3 03:44:38 EDT 2024] No API key specified for Namecheap API.
[Fri May  3 03:44:38 EDT 2024] Create your key and export it as NAMECHEAP_API_KEY
[Fri May  3 03:44:38 EDT 2024]
[Fri May  3 03:44:38 EDT 2024] Error add txt for domain:_acme-challenge.<FQDN of node>
TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup namecheap <FQDN of node>' failed: exit code 1

 

[Chris]

Hi - I'm running Proxmox 8.2.2 and running into the following odd error trying to provision certificates using the Namecheap ACME DNS Plugin. I believe this same configuration worked prior to the 8.2 upgrade within the last monthacme

1. Under Datacenter -> ACME, I've defined a challenge plugin using:
   1. Plugin ID: namecheap
   2. Validation Delay: 30 (default)
   3. DNS API: namecheap
   4. API Data:
      1. export NAMECHEAP_USERNAME="<username>"
         export NAMECHEAP_API_KEY="<validapikey>"
         export NAMECHEAP_SOURCEIP="<validsourceip>"
2. I validated that the username, api key and source ip work using the namecheap api directly using curl.
3. Under <node> -> System -> Certificates, I've defined a domain using:
   1. Challenge Type: DNS
   2. Plugin: namecheap
   3. Domain: <FQDN of node>
4. When I click "Order Certificates Now", I get an error with the following message implying that the API Data values are not being passed as expected (or that the API KEY itself is not being specified by the command):

Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/<redacted>/<redacted>
Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/<redacted>'
The validation for <FQDN of node> is pending!
[Fri May  3 03:44:38 EDT 2024] No API key specified for Namecheap API.
[Fri May  3 03:44:38 EDT 2024] Create your key and export it as NAMECHEAP_API_KEY
[Fri May  3 03:44:38 EDT 2024]
[Fri May  3 03:44:38 EDT 2024] Error add txt for domain:_acme-challenge.<FQDN of node>
TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup namecheap <FQDN of node>' failed: exit code 1

Hi,
please remove the export prefix for all the provided variables, they should be in KEY=VALUE format only as described in the docs https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_certs_acme_dns_challenge

Edit: fixed link

 

[reub]

Thanks, that worked. I had referenced the syntax in the plugin documentation referenced by that documentation but apparently incorrectly presumed the EXPORT needed in a shell environment was also necessary in the GUI. I don't know why it worked earlier. Perhaps I am misremembering the configuration.

Appreciate the help.