Proxmox worker deploy and test fail with Certificate Thumbprint error

[rogerfinch1231]

Hi

running Veeam 12.2 and Proxmox 8.3

deployed a worker to the Proxmox server using DHCP - amended the VM hardware to have the correct VLAN and took the MAC to set the correct IP in DHCP - so Veeam will connect to it, it'll upgrade itself online, and then it fails with a Certificate Thumbprint error- it doesn't like the certificate

so I look up the cert and it's one Veeam has created for this job. it's their own cert!

looking in the logs the only error listed is:

ERROR | [WorkerService][VCF]: Failed to obtain the endpoint: "No connected endpoint found."

both servers are on the same LAN and can ping etc - no firewall in the way.

this is on a Dell PowerEdge brand new server - 512Gb ram, 56 cores etc.

I originally tested Veeam and Proxmox on a MeLe mini pc - and that backed up fine. Not sure why it's broken on a real server?

the worker deployment needs to be fixed - as static IPs and static DNS just doesn't work as expected, and no VLAN option.

any ideas?

[PTide]

Hi,

I would appreciate if you could open a support case and post your case number so that we could troubleshoot the issue.

Thanks!

[rogerfinch1231]

Call 07507636

Logged over a week ago. No one seemed interested.

Thanks!

[rovshan.pashayev]

Hello Roger,

Please note that sharing the case number earlier would have allowed us to assist you more promptly.
It seems the support team is awaiting your response to their question - please follow up so they can assist you further.

[rogerfinch1231]

Hi

they asked if it was a firewall issue and I've replied it's on the same LAN - sat next to each other actually.

12 days and no real response isn't a great view of using this software for Proxmox.

I've removed the worker, and the Proxmox server, upgraded Veeam to 12.3 and retested and get the same error

the new certificate Veeam creates is using our *.domain.co.uk wildcard and the error shows it's not a suitable certificate for that purpose.

why is Veeam creating fake certificates based on our live wildcard certificate?! no wonder it's failing.

don't fill me with confidence when we ditch our VMWare for Proxmox.

anyone used any other backup solutions with Proxmox?

[PTide]

For future readers:

As I can see from the support case, the issue was with the certificate not meeting the requirements listed here.

Roger,

I doubt there are any 3rd-party enteprise-grade backup solutions for PVE out there, we were the first to introduce that level of support for PVE.
By the way, you might also want to post that question in Veeam User Group community.

Thanks!