make certificate error

haiwan

Well-Known Member
Apr 23, 2019
249
1
58
37
Hi! Have you been able to solve your problem? What version of Proxmox VE are you using?

Code:
pveversion -v
 
Code:
root@pve20:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-18-pve)
pve-manager: 5.4-11 (running version: 5.4-11/6df3d8d0)
pve-kernel-4.15: 5.4-6
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-53
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@pve20:~#
you check
no success
 
it's fixed in git already, and only affects the staging endpoint for now.
 
it's fixed in git already, and only affects the staging endpoint for now.
so we how to fix this?
Loading ACME account details
Placing ACME order
Order URL: https://acme-staging-v02.api.letsencrypt.org/acme/order/11858304/72614986

Getting authorization details from 'https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/35573847'
TASK ERROR: Error: GET to https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/35573847 { "type": "urn:ietf:params:acme:error:malformed", "detail": "Method not allowed", "status": 405 }
 
so we how to fix this?

Not using their staging environment or waiting for the fix to be shipped.
 
ok
so need how long time or if fix have notice

the production endpoint is not affected - for production usage you don't want to use the staging endpoint anyway, since it generates non-trusted certificates. the next update of libpve-common-perl should contain the fix.