Can't use ACME CA without ToS

d1nuc0m

New Member
Dec 6, 2024
10
3
3
Hi, I tried to add an ACME account with a custom directory (Serles ACME proxy, it redirects the request to an upstream CA from a private network) with:
Bash:
proxmox-backup-manager acme account register my-proxy.example.com email@example.com --directory https://my-proxy.example.com/directory

It fails as there are no ToS, even if this issue has been previously resolved, see #99102

PBS log:
Code:
Attempting to fetch Terms of Service from "https://my-proxy.example.com/directory"
Error: client error (Connect)

And on the other side there is a 404:
Code:
ERROR in flask_handlers: malformed (404): The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

That is true, as the endpoint does not have ToS info, only certs endpoint:
Code:
curl https://my-proxy.example.com/directory
{"newNonce": "https://my-proxy.example.com/newNonce", "newAccount": "https://my-proxy.example.com/newAccount", "newOrder": "https://my-proxy.example.com/newOrder", "revokeCert": "https://my-proxy.example.com/revokeCert", "keyChange": "https://my-proxy.example.com/keyChange"}


Packages
Code:
libproxmox-acme-plugins/stable,now 1.7.1 all [installed]
proxmox-archive-keyring/stable,now 4.0 all [installed]
proxmox-backup-client/stable,now 4.2.2-1 amd64 [installed]
proxmox-backup-docs/stable,now 4.2.2-1 all [installed]
proxmox-backup-server/stable,now 4.2.2-1 amd64 [installed]
proxmox-backup/stable,now 4.2.0 all [installed]
proxmox-default-kernel/stable,now 2.1.0 all [installed]
proxmox-grub/stable,now 2.12-9+pmx2 amd64 [installed]
proxmox-kernel-6.17.13-13-pve-signed/stable,now 6.17.13-13 amd64 [installed,automatic]
proxmox-kernel-6.17/stable,now 6.17.13-13 amd64 [installed,automatic]
proxmox-kernel-6.8.12-13-pve-signed/now 6.8.12-13 amd64 [installed,local]
proxmox-kernel-6.8.4-2-pve-signed/now 6.8.4-2 amd64 [installed,local]
proxmox-kernel-6.8/now 6.8.12-13 all [installed,local]
proxmox-kernel-7.0.12-1-pve-signed/stable,now 7.0.12-1 amd64 [installed,automatic]
proxmox-kernel-7.0.2-6-pve-signed/stable,now 7.0.2-6 amd64 [installed,automatic]
proxmox-kernel-7.0/stable,now 7.0.12-1 amd64 [installed,automatic]
proxmox-kernel-helper/stable,now 9.2.0 all [installed]
proxmox-mail-forward/stable,now 1.0.3 amd64 [installed]
proxmox-mini-journalreader/stable,now 1.6 amd64 [installed]
proxmox-network-interface-pinning/stable,now 1.0.3-1 amd64 [installed,automatic]
proxmox-offline-mirror-docs/stable,now 0.7.4 all [installed]
proxmox-offline-mirror-helper/stable,now 0.7.4 amd64 [installed]
proxmox-termproxy/stable,now 2.1.0 amd64 [installed]
proxmox-widget-toolkit/stable,now 5.2.5 all [installed]

Additional info - same issue does NOT happen on PDM, with these packages:
Code:
libproxmox-acme-plugins/stable,now 1.7.1 all [installed]
proxmox-archive-keyring/stable,now 4.0 all [installed]
proxmox-datacenter-manager-client/stable,now 1.1.4 amd64 [installed]
proxmox-datacenter-manager-docs/stable,now 1.1.4 all [installed]
proxmox-datacenter-manager-meta/stable,now 1.1.0 all [installed]
proxmox-datacenter-manager-ui/stable,now 1.1.2 amd64 [installed]
proxmox-datacenter-manager/stable,now 1.1.4 amd64 [installed]
proxmox-default-kernel/stable,now 2.1.0 all [installed]
proxmox-enterprise-support-keyring/stable,now 1.0 all [installed]
proxmox-geojson-data/stable,now 1.1 all [installed]
proxmox-kernel-7.0.2-6-pve-signed/stable,now 7.0.2-6 amd64 [installed]
proxmox-kernel-7.0.6-2-pve-signed/stable,now 7.0.6-2 amd64 [installed,automatic]
proxmox-kernel-7.0/stable,now 7.0.6-2 amd64 [installed,upgradable to: 7.0.12-1]
proxmox-kernel-helper/stable,now 9.2.0 all [installed]
proxmox-mail-forward/stable,now 1.0.3 amd64 [installed]
proxmox-mini-journalreader/stable,now 1.6 amd64 [installed]
proxmox-offline-mirror-docs/stable,now 0.7.4 all [installed]
proxmox-offline-mirror-helper/stable,now 0.7.4 amd64 [installed]
proxmox-termproxy/stable,now 2.1.0 amd64 [installed]
 
Last edited: