Troubleshooting

Start with Health and Activity

Read the current finding, its evidence, and the proposed next step. Activity combines installation progress, managed operations, and alerts. Exact metrics and technical evidence remain available when needed.

Do not retry blindly

A failed Save Changes or managed operation stays visible. Resolve the reported cause before building a new plan. Repeated retries cannot bypass a capability, generation, or safety gate.

Connection problems

• Check the server’s outbound DNS and HTTPS access.
• Confirm its clock is synchronized; signed reports and operations use bounded timestamps.
• Wait for the next five-minute monitoring report before declaring an enrolment stale.
• If managed control is unavailable but local access works, use WebAdmin reads or the documented root-only emergency exit.

Keep useful evidence

Record the time, server, visible finding, operation identifier, and exact stage that failed. Do not paste passwords, private keys, or raw business data into a support record.