jamesharr's latest activity
-
Jjamesharr replied to the thread PVE 9.2.10, LVM thick provisioning, snapshot-as-volume-chain, and cloud-init volumes.We also had an issue running backups with a qcow2-based CloudInit image ERROR: lvcreate 'local-blk-vg/vm-102-cloudinit.qcow2' error: Logical Volume "vm-102-cloudinit.qcow2" already exists in volume group "local-blk-vg" INFO: aborting backup...
-
Jjamesharr reacted to longer's post in the thread PVE 9.2.10, LVM thick provisioning, snapshot-as-volume-chain, and cloud-init volumes with
Like.
Take a look here, seems reported issue: https://lore.proxmox.com/all/20260817103032.73185-1-f.ebner@proxmox.com/T/#m98c8a1c78fcd2459239f87313331e81c062e1d5a -
Jjamesharr posted the thread PVE 9.2.10, LVM thick provisioning, snapshot-as-volume-chain, and cloud-init volumes in Proxmox VE: Installation and configuration.We're running PVE 9.2.10 on a test cluster and are experimenting with the snapshot-as-volume-chain tech preview feature. Our goal is to move away from thin-provisioned volumes while keeping support for snapshots when needed. One thing we found...
-
-
Jjamesharr replied to the thread ACME Order "Failed - server reply does not look like a PEM encoded certificate".A couple updates... - I can confirm what @tkell said, CertiNext seems to be working now. I tested on Proxmox-VE 9.2.3 and 8.4.19 - I contacted support a while ago and they have a patch in the works that will (eventually) make its way into the...
-
Jjamesharr reacted to tkell's post in the thread ACME Order "Failed - server reply does not look like a PEM encoded certificate" with Like.
@jamesharr I opened a support case with CertiNext, and as of today it appears they have fixed this issue. The Certinext API now returns a correctly-formatted certificate and the Proxmox ACME plugin accepts it and installs it.
-
Jjamesharr reacted to shanreich's post in the thread [SOLVED] Proxmox Firewall (nftables) troubleshooting with Like.
No, I didn't yet try it on newer kernels.
-
Jjamesharr replied to the thread ACME Order "Failed - server reply does not look like a PEM encoded certificate".We're running into this issue when using CertiNext. @Foorack's patch did the trick, but I know this will be overwritten as soon as we run through an upgrade. LetsEncrypt seems to return a cert chain formatted with a double-new-line (0x0a)...
