Thanks for keeping us posted, really appreciated here by all the team

@AtaxyaNetwork It will/it does

I have wondered this myself. [image: 1750783454921-screenshot-2025-06-24-124344.png] { "id": "0mcapon47", "properties": { "name": "Schedule sequence", "userId": "dbf49297-78e4-48c1-a996-a159343f89fe", "type": "xo:schedule:sequence", "progress": 67 }, "start": 1750780800006, "status": "success", "updatedAt": 1750782845608, "end": 1750782845608 } [image: 1750783475725-screenshot-2025-06-24-124427.png]

@florent Expected: Backup A (disabled) run first Backup B (disabled) will run after Backup A Backup C (disabled) will run after Backup B Outcome: All three backups ran in sequence as expected Thank you Florent for the help here

Excellent news, thanks for the feedback!

Yeah I remember it wasn't that easy

Hello @msupport we published a step by step guide, read more in the announcement there https://xcp-ng.org/forum/post/94268

@olivierlambert Thanks!

haha we were all noobs when we started, it's fine

@olivierlambert I’ve got a few VM’s that lock up from time to time. There is no rhyme nor reason (different hosts, different storage, etc). As a result, I just have a job that restarts them at 5:30 am every day. I’d like to have the software tool software restart them but, in the occasion wher the VM is locked up tight as Fort Knox, I’d like the hard reset to happen. Make sense ?

@cocoon hello! For now we are on reflexion on a refactoring to move towards a system more RBAK based, IAM type. We will inform the whole community when we are sure of the direction the new ACL system will take. Stay tuned

removed the failed server connection. Restarted xo-server service. Added new host again. Seems fine now. In hind sight, I could have very well recycled a DHCP ip here as well, if that is a known issue...

Sounds a like a bug to me, we can maybe check what's displayed in there and take a look at xe level to see what's the problem Ping @lsouai-vates

@olivierlambert deploying fresh copy worked and registered under different email. Thank you for assistance

Great, thank you!

@kagbasi-ngc said in VM Console Screen Suddenly Inaccessible: Hmm, interesting observation about potentially this being a failed migration issue. I can confirm that none of my users in the lab are migrating any VMs or this particular one, for that matter. However, I do have the Load Balancer plugin running and it could be the source of a migration that could've failed. How can I confirm this in the logs? I mean, what should I be looking for? While trying to find logs, you can try to find the VM in question and see if it is using local storage rather than shared.

This page is being improved as we speak It shouldn't be in "Future improvements" because it's here

Excellent news, thanks!

Sorry I don't see any error, it's just a message from the GC. However, I have to admit I don't have time to take a deeper look myself. If you have support, might be the right time to open a ticket, alternatively someone will take a look when they can