Skip to content
CortexDocs

Defender troubleshooting

Troubleshoot Defender connections, capture, and workspace sync, then send diagnostics to the Chaos Labs team if it still does not work.

If an app is not capturing, open it from Home or Connections, review its configuration and recent activity, then follow the displayed recovery action. Use the connection's Health section for checks and Settings for workspace identity, updates and diagnostics.

  1. Open the affected app from Home or Connections.
  2. Review its configuration and activity, then select Check health when available. Confirm a successful health-check result before continuing.
  3. If configuration no longer matches Defender, use the displayed recovery action and review the proposed changes. See Manage app connections.
  4. Restart the app only when Defender asks, then send a new prompt.
  5. Verify capture and sync, including the matching record in Atlas. Activity captured on the device alone does not prove delivery.
Share diagnostics from SupportManage devices in Cortex

Repair browser sync

Open Browser sync on Home to reach Browser connections. Review Health, including browser routing, certificate trust and the browser relay. Use Check health, Turn on routing or Install certificate when offered, then test a new prompt in a supported browser.

Review browser certificate trust and relay healthManage devices in Cortex

See Set up browser sync for routing and trust recovery. If the control is disabled, follow the linked recovery guide.

Get diagnostics help

Open Settings → Support → Share diagnostics. To send a report yourself, select Copy diagnostics in the dialog, wait for a successful copy and review the details before sending them. If sharing fails, the action does not establish that support received the report. Include the source, approximate test time, expected result and actual result when contacting support@chaoslabs.xyz. Do not include credentials. See Settings and updates.

Local port conflicts

Defender diagnostics can report a local conflict, such as failed to bind PAC HTTP server: or another agent-rs instance holds the store lock. If the error names a local port or process, include those details in the support request. Developers can use Fix Cortex Defender port conflicts.

Where to check status

DestinationUse it for
Home → app or Connections → appConfiguration, recent activity and recovery actions
Home → Add connectionBrowse available sources and open setup
Home → Browser sync → Browser connectionsBrowser routing, certificate trust and relay health
Connection → Health → Check healthReported checks for the selected source
Settings → SupportShare diagnostics
Settings → WorkspaceRead the reported organization and identity
Settings → GeneralVersion and update checks
Settings → Danger zoneStop or start Defender and verify the resulting state
Cortex Atlas → user profileConfirm delivery and attribution of test activity