@simonp I'm not sure which one as I can see 2 config.tom file. 1st is under "/root/.config/xo-server/" config.toml.txt 2nd is under "/opt/xo/xo-server/" config.toml2.txt Both config.toml attached. Thank you. Best regards, Azren

@Danp I was going to do the upgrade over the December / January Christmas break in Australia but that is when this issue became apparent so we didn't want to be making major changes until it was resolved. I note @anthoineb noted the first report was late August / September 2025 which was just before 8.2.1 reached EOL, so it would be a shame not to have a fix for it tested on 8.2.1 as it seems an upgrade to 8.3 would be unwise while we still have this issue?

@olivierlambert Fun fact -lah is short for lazy ass human AI is coming... [image: 1761837446934-feb6ff1a-7269-4c37-84b8-8ed1d64c3d68-image.png]

If XO from sources, double check you are fully up to date in the first place. You maybe used an outdated V2V code that wasn't asking for the template, causing the issue you experience now.

Then reboot than broken host and in the meantime, re-issue the power reset command from the master.