Certificates renew not Possible

[Meik]

Hi @all

one of my nodes did not renew the Certificate .

Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/55....52/893.....526

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/109....71566'
The validation for h02.mydomin.nix is pending!
[Mon May 23 03:51:40 CEST 2022] You don't specify autodns user, password and context.
[Mon May 23 03:51:40 CEST 2022] Error add txt for domain:_acme-challenge.h02.mydomain.nix

TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup autodns h02.mydomain.nix' failed: exit code 1

The "You don't specify autodns user, password and context." is specified:
export AUTODNS_USER="login@mydomain.nix"
export AUTODNS_PASSWORD="SuperDuperExtraHeftigPassword"
export AUTODNS_CONTEXT="4"

This has word before several times.
I have Create a new Challenge-Plugin Configuration on the Cluster, this did not work too.

Where can i look for debugging? Or temporary back to HTTP-Challenge?

Thanks for Help - Meik

 

[fabian]

you don't need to export those anywhere, just configure the Acme plugin accordingly..

 

[Meik]

Hi Fabian,

if I set the credentials without "export", there is a new "message":

Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/550...52/8933....526

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/109...87..66'
The validation for h02.mydomain.nix is pending!
[Mon May 23 16:17:54 CEST 2022] invalid domain
[Mon May 23 16:17:54 CEST 2022] invalid domain
[Mon May 23 16:17:54 CEST 2022] Error add txt for domain:_acme-challenge.h02.mydomain.nix
TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup autodns h02.mydomain.nix' failed: exit code 1

Thanks for your help - Meik

 

[fabian]

that means that with your given user/password/context, there is no zone matching your domain.. maybe check on the other end if all the permissions/settings are correct and if there are any logs (and double check that the user/password is correct and works)?