I make it the other way, I add a tag for the VM I want a health check to happen, and no tag if I don't want a health check.

Then, in the backup's schedule, I add my tag:

I'm gonna try the same and will let you know.

@olivierlambert
Yes, confusing, indeed
I just now restarted XO and the toolstack one more time to be sure. Yesterday, it was OK at the beginning but the issue reappeared after a few hours.
I'll let you know ASAP.

@olivierlambert
I mean if use commit 0ccfd4b, there is no issue, if I use a more recent one, like the latest 583c7, the issue is appearing.

@14wkinnersley
That issue is definitely coming from XO from source, it does not appear with XOA.

I revert my XO to commit 0ccfd4b and now everything is back to normal.

I don't know if our issue is also related to self-signed cert, but there's been other issues with latest commit of XO, we should stick to that version until a solution is implemented.

Same issue on my host, with commit 8e5d9.
I tried the health check, and it is stuck.
I do not see any error message, the log just says pending.

I tried a restore check with XOA 5.91.2, no issue on that side, only XO from source seems to be not working.

@MathieuRA
OK, thanks for the answer.

Looking forward for XO6

Thanks for the info and the faster than light answer ️

Have you enabled uefi and secure boot for that VM (in the Advanced Tab)?

@florent
Hi Florent,

The imported VM was definitely not in DHCP mode, it was a static address.
I have an XOA and XO from source, but we already re-purposed our VMware server, so sadly I can't help you debugging anymore.
Maybe you can do that with the original poster of this thread?