DocumentationTroubleshooting

Troubleshooting

Troubleshooting

Messages from the console and the agent, what they mean and how to respond. Followed by known functional limits of the Windows and Linux agents.

This page lists the most frequent situations encountered during operation. Each message is reproduced as is. The right column indicates the expected action.

Console messages

The console shows precise messages when an action fails or a value is missing. It never fabricates a value the server did not provide. A dash or the Not available label indicates absence.

Common console messages and situations.
MessageWhat to do
"You do not have the rights required for this action."Your role does not allow it. Ask the tenant administrator to review the group-to-role mapping.
"Your session has expired. Sign in again."Sign in again. Unsaved changes are lost.
"The item changed in the meantime. Reload then retry."Someone else modified the item. Reload the page before retrying.
"The action could not be confirmed. Check its state before retrying."The server did not confirm. Reload and check whether the action was recorded before replaying it.
"Data unavailable"Click Retry. If the error persists, notify your operator.
"Unit masked across n events on this page"The unit for these events covers fewer than k people. It is masked, events remain listed.
"No data for this period with these filters."Widen the period or remove filters.
Value "Masked"Group of fewer than k people, masked to protect individuals.
"Not computable"Rate without denominator for the period, for example no entity detected.
"Handed to the device, result not reported"The action was handed to the device, which does not report back. Check its effect on the device page.

Special value states

Four states must not be confused. Each carries a precise meaning in tables and exports.

  • 0 : actual measure, the counter is zero for the period.
  • Absent, dash or Not available : the server did not provide the value.
  • Masked : the underlying group covers fewer than k people; the value is masked to protect individuals.
  • Not computable : rate or ratio without a denominator, for example no entity detected.

Agent no longer redirecting

When the agent stops redirecting, the most common cause is a driver that no longer answers the service, or a conflict with another network layer. Behaviour depends on the configured mode.

  • fail-open : the driver stops redirecting. Traffic goes out without inspection. An event is written.
  • fail-closed : only the IPs of known AI services are blocked. The rest of the traffic passes. An event is written.
  • Restart the agent service. If the driver does not load, check the Windows or Linux logs.
  • Check channel state in the console: an inactive channel is never decrypted.

Non-inspectable application

Some applications reject the local CA certificate. They pin certificates. The agent flags them as non-inspectable and applies the configured policy.

  • Relay : the connection passes without inspection, an event is written once per day per process-domain pair.
  • Block : subsequent connections from that pair are blocked, an event is written.
  • Extension : for browsers, falls back to the policy-deployed fallback extension.

Device enrolment

  • Expired token : enrolment tokens are single-use and valid for 24 hours. Request a new token from the console.
  • Consumed token : a token can only be used once. Generate a new one for each device.
  • Clock drift : a drift greater than five minutes against the server breaks mutual TLS enrolment.
  • Unknown licence public key : the licence was issued for a different tenant. Check the tenant identifier.

Functional limits of the Windows agent

The current Windows package does not yet cover every scenario. Here is what is inspected and what is not in preproduction.

  • The Web interface channel is protected for catalogue services.
  • The Desktop application channel has no catalogue entry yet. WFP redirection and TLS relay work, but no DLP blocking is applied to the content of these applications.
  • The Code assistant channel has no IDE entry shipped in the default catalogue.
  • Preproduction drivers are test-signed. Enabling testsigning is required and disables part of the Windows boot protections.
  • Browsers installed outside the system MSI, for example from the Store, may need a dedicated policy to trust the local CA.

Functional limits of the Linux agent

  • The Web interface channel is protected for catalogue services, in Chrome .deb and in the Ubuntu Firefox Snap.
  • Browsers installed as Flatpaks have their own trust store. They are not covered by the current build.
  • OCR for scanned PDFs and images is not available on Linux in this build.
  • The Desktop application channel has no catalogue entry: redirection is validated, not DLP blocking of content.
  • Linux ARM64 is not shipped. Only x86_64 is available.

Local store and retention

The agent stores events in an AES-256 encrypted SQLite database on the device. Default retention is 90 days or 2 GB, whichever comes first. Both values are configurable.

  • Events are chained with HMAC-SHA-256 and anchored by signed time seals.
  • No sensitive value is ever written to the local store. Only detection metadata is kept.
  • Past the limit, the oldest events are purged.