ACME certificates & AutoDNS - configuration question

Spacey

Renowned Member
Sep 6, 2013
17
5
68
Hi!
In general I've got ACME & AutoDNS working on my pfSense FW - so I guess it should work in general.
I'm now in my MailGateway configuration and try to configure the ACME AutoDNS challenge plugin. But what do I need to enter into the API Data form field?

I tried

Code:
AUTODNS_USER="AutoDNS username"
AUTODNS_PASSWORD="AutoDNS password"
AUTODNS_CONTEXT="4"

... but doesn't work. The message I get when trying to renew API/SMTP cert:

Code:
Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/1234/5678

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/1234'
The validation for proxmox.mydomain.de is pending!
[Mon Sep 25 14:43:39 CEST 2023] invalid domain
[Mon Sep 25 14:43:39 CEST 2023] invalid domain
[Mon Sep 25 14:43:39 CEST 2023] Error add txt for domain:_acme-challenge.proxmox.mydomain.de
TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup autodns proxmox.mydomain.de' failed: exit code 1

Any idea where to look?! Thx!
 
No... not really. I switched back to HTTP mode and opened the port 80 for that :(
 
Quick Update on the AutoDNS Login Issue:

After some debugging, it was identified that the issue stemmed from the use of quotation marks (" and ') in the environment variables within the dns_autodns.sh script.

Original Variables:​

Code:
AUTODNS_USER="AutoDNS username"
AUTODNS_PASSWORD="AutoDNS password"
AUTODNS_CONTEXT="4"

Issue:​

Including quotation marks in the XML request for AutoDNS login led to a failed login attempt with the error message: "User does not exist or password incorrect."

Solution:​

Removing the quotation marks from the variables resolved the issue, enabling successful AutoDNS login on Proxmox VE (PVE).

Code:
AUTODNS_USER=AutoDNS username
AUTODNS_PASSWORD=AutoDNS password
AUTODNS_CONTEXT=4

Hope this helps anyone encountering a similar issue!
 
Last edited:
  • Like
Reactions: Cleaner
hi,

I had also issues, with invalid domain: Issue was, my password was too "complicated" and it seems, that one of chars broke the process. So I generated the password without bad things, like @ / # / $ .... and then it worked.