PVE Jobs Failing after CVE-2025-48983 patched (12.3.2.4165)

[Barker]

I can't tell if this is coincidental or not, but right after I upgraded to 12.3.2.4165 to patch a vunerability reported by Veeam, I started getting "Unable to get Path Commander" errors on some (not all) Proxmox backups.

I tried creating a new repo, new job, rebuilding the workers, removing all traces of backups for these problematic VMs, to no avail.

I originally thought it was related to a single proxmox node, as I was only getting this error on (all) VMs hosted on one of 3 of our nodes, but I tried migrating the VM to another node (that has jobs processing without errors) and I still get the "Unable to get Path Commander".

I upgraded to 13 to see if that would make any difference, but it's having the same behavior.

I'm working with our service provider to get a ticket opened (it turns out if you are using a rental license provided by a service provider, you aren't able to open cases?!?), but at the moment I was hoping someone may know what this "Unable to get Path Commander" error means, and why it would affect only some of my proxmox servers. The VMware servers are all fine also.

[Gostev]

Please read the first paragraph of the forum rules and don't just ignore it in future.

When an issue happens on some VMs only, it's a strong indication of an environmental issue.

Rental license keys must be bundled within managed service offerings and cannot be resold as standalone products. Based on your surprise and the fact that you've been personally troubleshooting the issue all this time, your service provider might be violating the licensing policy.

[Barker]

Thank you for your response. Our service provider said they can open a ticket on my behalf to troubleshoot this.