Search results

  1. M

    Boot Failure on upgrade to VE 7.2 with kernel 5.15.35-1-pve

    Scrub was completed without errors. Disk still shows up and no errors. Setting `intel_iommu=on iommu=pt` seems to be the solution, at least for me.
  2. M

    Boot Failure on upgrade to VE 7.2 with kernel 5.15.35-1-pve

    I'm suffering from the same problem. I'm using a microserver gen8 (BIOS (legacy) only unfortunately. The SSD in question is connected to P222 raid card in HBA mode. Setting `intel_iommu=on iommu=pt` seems to have fixed it for me. It's not spewing errors and although it reported it could not...
  3. M

    No autorenewal for Let's encrypt certificate with DNS challenge plugin

    Beat me to it, just noticed while running updates this was indeed fixed. Never got any reply from anyone (community or staff) and didn't see a fix in the first few updates that came along, so I just assumed I was screaming into the void Many thanks for your reply though!
  4. M

    No autorenewal for Let's encrypt certificate with DNS challenge plugin

    I was just notified my certificate is going to expire soon again. Are the devs aware of this issue? Is it possible anyone can point them towards this thread or point me towards them? It would be possible for me to open a PR for this issue, except I'm unaware where to send it.
  5. M

    No autorenewal for Let's encrypt certificate with DNS challenge plugin

    I've just done some more testing pvenode config get --property acme Returns empty. I think this is why if ($node_config && $node_config->{acme}) evaluates to false. This is due to me only using acme dns challenge. A HTTP challenge would go into acme. a DNS challenge goes into acmedomain0...
  6. M

    No autorenewal for Let's encrypt certificate with DNS challenge plugin

    A couple of months ago I've added Let's encrypt certificates to my cluster of PVE nodes. I've followed the documentation as far as I could and everything worked fine until a little less than 30 days ago. I suddenly got an e-mail saying my certificates were up for renewal and noticed they...
  7. M

    unable to install: "no cdrom found"

    First post here, quickly wanted to reply i encounter this issue a lot. Sometimes it finds it sometimes not. I found that pulling the usb when it first reports "waiting for 5sec" and then immediately reinserting it fixes it for me

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!