Client offline or unable to report

Determine whether the failure is local, farm-wide, regional or Server-side.

Read-only checks

• Run rigectl status, inspect the service journal and resolve every configured access endpoint.
• Test TCP/TLS and a small authenticated request path separately.
• Inspect disk space, time synchronization, route, DNS and retransmissions.

Interpret errors

• Connection refused usually means the remote listener or route actively rejected the connection.
• Timeout while awaiting headers may be a path, proxy or overloaded upstream issue.
• Repeated DNS timeout must be solved before changing Client retry behavior.

Avoid

• Do not restart repeatedly before preserving the first useful log.