Let's encrypt cert renewal task stopped working

reelwm

New Member
Apr 20, 2023
3
0
1
Hi everyone,

I had a look at the task log of my PMG 7.3-3 and realized, that the acmerenew task stopped working.

In the column "Status", I can see:
"ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup hetzner host.domain.tld' failed: exit code 1"

The whole output is:

Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/#########/############ (order numbers masked for privacy reasons)

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/############'
The validation for mail.iw54.de is pending!
[Thu Apr 20 10:25:47 CEST 2023] You didn't specify a Hetzner api token.
[Thu Apr 20 10:25:47 CEST 2023] You can get yours from here https://dns.hetzner.com/settings/api-token.
[Thu Apr 20 10:25:47 CEST 2023] Error add txt for domain:
TASK ERROR: command 'setpriv --reuid nobody --regid nogroup --clear-groups --reset-env -- /bin/bash /usr/share/proxmox-acme/proxmox-acme setup hetzner host.domain.tld' failed: exit code 1

The configuration of the hetzner acme plugin with the correct dns api token was not changed. The only things that changed were caused by updates installed via administration UI.
I created a new hetzner acme plugin configuration with a freshly generated api token, but no success as well.
Could it be, that the scripts used by the task were updated and now are broken?

Hints, what I can do to make it working again, are highly appreciated! Many thanks in advance,
reelwm
 
Last edited:
AFAIK, there was no recent change there

can you post the config (anonymized of course) ?
 
Yes, of course!
Please find attached the screenshots.
 

Attachments

  • Account.png
    Account.png
    13.7 KB · Views: 12
  • DNS-Plugin.png
    DNS-Plugin.png
    14.9 KB · Views: 12
Many thanks, Dominik,

that fixed my issue!
I'm wondering, how this could have worked before - I'm convinced, that I used the token without the prefix "HETZNER_Token=".

Anyway, now it works again - thumbs up!

Kind regards,
reelwm
 

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!