Troubleshooting a TurtiniOS appliance

Common issues and where to look, from the Cloud module and on the machine.

A node isn't showing in the fleet:
• Confirm the node booted and its agent is running.
• Confirm it's pointed at the same fabric (address + enrollment token) — see "Connecting a node to the fabric."
• Confirm it's on a reachable network. Nodes that fail identity verification are refused.

A server isn't offered as a hypervisor host:
• Confirm hardware virtualization is enabled in firmware.
• Confirm the node is a server role and joined to the fabric.
• Give it a few seconds after boot to advertise; then check the Hosts tab.

A VM is stuck in "pending":
• Its host may be offline or stale — check the Hosts tab. Pending means the host hasn't picked the VM up yet; it will as soon as it's back.
• Check the VM row for an error message.

The console won't open:
• If it says the console bridge isn't configured, run the console secret provisioning once — see "Provisioning the VM console secret."
• The VM must be running to have a console.
• The host must be reachable from the web front door on the console port.

A machine rolled back after an update:
• That's the health gate doing its job — the new version didn't come up healthy, so it reverted to the last known-good one. Check the machine's boot health output for which service failed, fix the cause, and try the update again. Your data is unaffected.

Everything is offline but seems fine:
• That's expected — TurtiniOS runs fully offline. It reconciles with the cloud only when a link is available.