Repair a reported problem

Before you start

  • You need the viewer role or a higher role to read messages.
  • You need permission to change the affected object or its source configuration.

Follow a diagnostic message

  1. Open System > Diagnosis, or click the message badge in the top bar.
  2. Read the message level and code.
  3. Read the description and any repair hint.
  4. Open the affected object with the message's link.
  5. Correct the cause at the object's configuration source.
  6. Return to Diagnosis after the node checks again.

Diagnosis with an invalid entry error, an unreachable list warning and a policy priority notice.

Figure 1. Each message identifies the problem and the affected object.

Example codeAction
InvalidEntriesOpen the list source and correct the named invalid line
ListUnreachableCheck the source URL and network access from the node, then refresh the list
PriorityTieGive matching policies different priorities

An error means something does not work. A warning needs investigation. An info message provides context. Messages disappear when their cause disappears; dismissing a browser notice does not repair the configuration.

Check the result

The message disappears after the correction and the next check. Test the affected DNS behavior with Tools. Use the troubleshooting reference if the cause remains unclear.

Source: docs/guide/dashboard/diagnosis.md