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

reub

New Member
Mar 30, 2024
2
0
1
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):
Code:
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 - 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):
Code:
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
 
Last edited:
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.
 
Hi,
I'm using the same method for namecheap and my configuration as below;

Code:
NAMECHEAP_USERNAME="myusername"
NAMECHEAP_API_KEY="my_api_key"
NAMECHEAP_SOURCEIP="my_whitelisted_ip"

but it returns ;

Code:
[Thu Jul 11 11:40:24 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:24 +03 2024] API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] invalid domain

checked with namecheap and they say api id is valid and active, also when i curl the https://api.namecheap.com/xml.response? with necessary parameters it works without any error but somehow seems like namecheap plugin sends my api key wrong.

How i can debug and solve it?
 
Hi,
I'm using the same method for namecheap and my configuration as below;

Code:
NAMECHEAP_USERNAME="myusername"
NAMECHEAP_API_KEY="my_api_key"
NAMECHEAP_SOURCEIP="my_whitelisted_ip"

but it returns ;

Code:
[Thu Jul 11 11:40:24 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:24 +03 2024] API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] invalid domain

checked with namecheap and they say api id is valid and active, also when i curl the https://api.namecheap.com/xml.response? with necessary parameters it works without any error but somehow seems like namecheap plugin sends my api key wrong.

How i can debug and solve it?
Hi,
do you have the correct plugin settings? Make sure to add an ACME DNS plugin using the DNS API namecheap in Datacenter > ACME and use that plugin on the per node certificate configuration.
 
  • Like
Reactions: sheshman
Hi,
do you have the correct plugin settings? Make sure to add an ACME DNS plugin using the DNS API namecheap in Datacenter > ACME and use that plugin on the per node certificate configuration.
Sorry to forgot mention i'm trying this on proxmox mail gateway 8.0.3 so there are no Acme option on pmg, but i've attached screenshot of my plugin's config, and sorry again that i realised that i posted this on wrong topic, i must post in pmg section.
 

Attachments

  • 001.png
    001.png
    35.8 KB · Views: 35
Hi,
I'm using the same method for namecheap and my configuration as below;

Code:
NAMECHEAP_USERNAME="myusername"
NAMECHEAP_API_KEY="my_api_key"
NAMECHEAP_SOURCEIP="my_whitelisted_ip"

but it returns ;

Code:
[Thu Jul 11 11:40:24 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:24 +03 2024] API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:25 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] error API Key is invalid or API access has not been enabled
[Thu Jul 11 11:40:26 +03 2024] invalid domain

checked with namecheap and they say api id is valid and active, also when i curl the https://api.namecheap.com/xml.response? with necessary parameters it works without any error but somehow seems like namecheap plugin sends my api key wrong.

How i can debug and solve it?

Remove the quotation marks. Worked for me.
 
  • Like
Reactions: sheshman

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!