Hi
We have recently found that our DNS provider is supported in the PVE ACME client and we did therefore configure it according to the documentation
Since the provider does not yet have specific form fields configured, we simply added the environment variables (for use with acme.sh) as key-value pairs in the "API Data" field and attempted to get certificates.
The attempt failed as the client could not fetch the API Access Token for our provider.
We then investigated further and found that if we used acme.sh directly on a server, the credentials provided do work and we get a certificate issued to us.
This is how the data is specified in the "API Data" field
The actual contents have been replaced with three dots for security reasons.
Is there anything else to do with this or is it supposed to work.
Here is btw. the output of pveversion -v
We have recently found that our DNS provider is supported in the PVE ACME client and we did therefore configure it according to the documentation
Since the provider does not yet have specific form fields configured, we simply added the environment variables (for use with acme.sh) as key-value pairs in the "API Data" field and attempted to get certificates.
The attempt failed as the client could not fetch the API Access Token for our provider.
We then investigated further and found that if we used acme.sh directly on a server, the credentials provided do work and we get a certificate issued to us.
This is how the data is specified in the "API Data" field
Code:
CURANET_AUTHCLIENTID="..."
CURANET_AUTHSECRET="..."The actual contents have been replaced with three dots for security reasons.
Is there anything else to do with this or is it supposed to work.
Here is btw. the output of pveversion -v
Code:
proxmox-ve: 8.2.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-2
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph: 18.2.2-pve1
ceph-fuse: 18.2.2-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.3
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.1
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.13-2
pve-ha-manager: 4.0.5
pve-i18n: 3.2.3
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1