@jcdick1 I run opnsense on xcp-ng personally as well and use their packaged tools without issue, the only time I've gotten this behavior is when I hot-added interfaces and it changed the order of interfaces. If that's not it, I'm really not sure what would be causing this One last thing you can try in case it's a weird cash issue is (inside XOA) go to settings > servers, click the green connected button next to your xcp-ng server to disconnect it from xoa - then wait a couple seconds and click it again to reconnect it

I agree, I don't think it's a technical limitation, just a use case not "covered"

@Darkbeldin I wasn't sure about turning on two-factor. I went through that process and generated the "app password" and it seems to be working. Thanks for the info!

@jcdick1 I have almost the same servers and everything has been fine (without keyboards)... HP DL360p G8 with E5-2680 v2 and also some with E5-2680 (not v2). I did have one machine have problems but it was hardware failure (CPU fault), not XCP. These HP G8 machines are about a decade old now, so hardware issues are not a surprise.

What do you mean by running an update? Did you git pull and rebuild?

It's in our documentation, please read https://xen-orchestra.com/docs/configuration.html#https

I ended up restarting the toolstack, which caused all of the migrating VMs to be in an error state, as they were halted but the system thought they should be running. I couldn't perform any actions on them. VM_BAD_POWER_STATE(OpaqueRef:f1f14751-cbc8-4a86-b98f-9e980b2b0d00, Running, Halted) After restarting the toolstack on all the hosts in the pool, they finally showed up as powered off and I was able to get them back up and could migrate them. Is there anywhere I can look to see why the migration got right to the doorstep and stopped?

Disconnect and reconnect the server in Settings/server of XO.

See also: https://xcp-ng.org/forum/post/21792

Hi, Before reporting on issues when you use XO from the sources, you must always fetch the latest code available on GitHub. Because it's likely some issues are fixed since then. Please upgrade, and come back if the problem persists

It depends where you decided to install it (basically where you cloned to repo). Also remove the redis database if it's only used for XO.