ACME Cert Order Not Working

[duluxoz]

Hi All,

I'm trying to set up a private PKI (Step-CA: stepca.example.com) to provide my PVE (Proxmox v18.2.4) with certificates.

I have the Step-CA server set up and working (I can receive/renew certs via ACME.sh from a different server to the stepca.example.com).

I have run the command:

pvenode acme account register my_acme root at example.com  --directory https://stepca.example.com/acme/my_acme/directory

and this returned:

Attempting to fetch Terms of Service from 'https://stepca.example.com/acme/my_acme/directory'..
No Terms of Service found, proceeding.
Attempting to register account with 'https://stepca.example.com/acme/my_acme/directory'..
Generating ACME account key..
Registering ACME account..
Registration successful, account URL: 'https://stepca.example.com/acme/my_acme/account/PLeTGsgGbogPgnURjpYMuieKc1Yj2cFQ'
Task OK

Running the command:

pvenode acme account info my_acme

returns all the correct information (as above) - the most important part is:

status: valid

However, when I then run the command:

pvenode acme cert order

I receive:

Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/API2/ACME.pm line 196

Also, when I run the command:

pvenode acme cert renew

I (as expected) receive:

No current (custom) certificate found, please order a new certificate!

Finally, when I run the command:

pvenode cert info

I receive info only about the "pve-root-ca.pem" and "pve-ssl.pem" certificates (again, as expected).

So, if someone could be kind enough to let me know where I've gone wrong, I'd appreciate it.

Cheers

Dulux-Oz

PS: Also, the (on-line) Proxmox doco says (in section 3.12.4. Trusted certificates via Let’s Encrypt (ACME) ) that "You can register and deactivate ACME accounts over the web interface Datacenter -> ACME...", but I can't find that in the Web Interface - has something changed in recent versions of ProxMox?