When I try to add a new ACME account for PBS I am unable to register a new account, from my reading on various forum posts here I should only be utilising the default account via the CLI only (as the option is missing from the GUI, I've also tried other combinations of accounts and emails) and even if there is no TOS it should create the account anyway. Updated packages today but I still receive the following error:
root@pbs:~# proxmox-backup-manager acme account register default info@example.com
Directory endpoints:
0) https://acme-v02.api.letsencrypt.org/directory
1) https://acme-staging-v02.api.letsencrypt.org/directory
2) Custom
Enter selection: 2
Enter custom directory URI: https://freeipa-fqdn/acme/directory
Attempting to fetch Terms of Service from "https://freeipa-fqdn/acme/directory"
Error: missing field `keyChange` at line 1 column 382
On another post the following command was also requested and executes without error for me:
pvesh get /cluster/acme/meta --directory "https://freeipa-fqdn/acme/directory" --output-format json-pretty
{
"caaIdentities" : [
"example.com"
],
"externalAccountRequired" : false,
"termsOfService" : "https://www.example.com/acme/tos.pdf",
"website" : "https://www.example.com"
}
Has anyone had this issue before?
root@pbs:~# proxmox-backup-manager acme account register default info@example.com
Directory endpoints:
0) https://acme-v02.api.letsencrypt.org/directory
1) https://acme-staging-v02.api.letsencrypt.org/directory
2) Custom
Enter selection: 2
Enter custom directory URI: https://freeipa-fqdn/acme/directory
Attempting to fetch Terms of Service from "https://freeipa-fqdn/acme/directory"
Error: missing field `keyChange` at line 1 column 382
On another post the following command was also requested and executes without error for me:
pvesh get /cluster/acme/meta --directory "https://freeipa-fqdn/acme/directory" --output-format json-pretty
{
"caaIdentities" : [
"example.com"
],
"externalAccountRequired" : false,
"termsOfService" : "https://www.example.com/acme/tos.pdf",
"website" : "https://www.example.com"
}
Has anyone had this issue before?