Troubleshooting & Diagnostics
Start on Endpoints → Health. Every device reports every 60 seconds, and each column points at a specific part of the agent:
| Column | Healthy | If not |
|---|---|---|
| Enrolled | ✓ | self-signed — the device has not enrolled. Check the enrollment profile or setup script reached it. |
| Capture | on | See Browser capture. |
| Hooks | managed | See Hooks. |
| Policy files | locked (if you enabled the lock) | N writable — the user can edit local policy state. |
| Creds | ✓ | Credentials missing — re-run enrollment. |
| Uploading | 200 | 401×N — the device's key was revoked or replaced; re-enroll. stale Nm — nothing delivered for over 15 minutes. |
| Services | 3/3 | A required Waxell service is down. |
| Self-heal | — | The uploader has been restarted N times — persistent crashes. |
| Beacon | under a minute | Stale after 5 minutes: the device is off, offline, or the agent stopped. |
A device is degraded when it is not enrolled, has no credentials, has a required service down, cannot deliver, or has coding-agent hooks without the blocking event registered.
Browser capture
| State | What to do |
|---|---|
| held | Working. Browser capture is off for this device on the Guard, so captures stay on it. |
| n/a | No browser AI activity yet. Use an AI site and check again. |
| no ext | The agent has never received anything from the extension. Follow the no-ext checklist — most often an application-control tool (ThreatLocker, AppLocker, WDAC) is blocking WaxellBrowserBridge.exe, which the browser starts through cmd.exe. |
| on · Edge uncovered | One browser with encrypted DNS has not reported in. Check the extension is installed in that browser. |
| dark | The extension stopped reporting more than a day ago. Check it was not removed or disabled. |
Hooks
| State | What to do |
|---|---|
| none / no PreToolUse | Reinstall or upgrade the agent; it re-registers hooks at install and repairs them continuously. On Windows, check application control allows wax-hook.exe. |
| n/9 | Some events missing — usually a tool update rewrote its settings. The agent repairs this on its next pass. |
| guard | Hooks are registered at user level rather than managed. Upgrade the agent to move them to the managed location. |
macOS
Network extension never activates. On a Mac that was not enrolled through
Apple Business Manager, approve it once: System Settings → General → Login
Items & Extensions, enable Waxell, then Allow. The app must be in
/Applications.
No flow metadata. The content filter is configured by the flow visibility
profile. Check it is installed: sudo profiles list -all | grep -i flowsprofile.
An activated system extension alone does not mean the filter is configured.
Sign-in never returns to the app. Quit and reopen Waxell Setup (it
re-registers its waxell:// link on launch) and sign in again.
Logs: the app's Troubleshoot tab, or Console.app filtered to dev.waxell.
Windows
Services.
sc query WaxellNetworkMonitor
sc query WaxellPolicyDaemon
Both should be RUNNING. If one is missing after install, check your antivirus
or application-control history for a blocked or quarantined Waxell executable and
allow C:\Program Files\Waxell\.
Sign-in never returns to the app. Close and reopen Waxell Setup and sign in again.
Logs: C:\ProgramData\Waxell\service.log
Get-Content 'C:\ProgramData\Waxell\service.log' -Tail 50
Memory Integrity (HVCI). With Memory Integrity on, Windows blocks the driver Waxell uses to read HTTP/3 hostnames, so that one metadata signal is missing. Browser capture, hooks and policy are unaffected. No action needed.
Encrypted DNS (DoH)
When a browser uses DNS-over-HTTPS, the network monitor cannot see which AI sites it reaches. Browser capture is unaffected, because the extension reads the page. The device page and Health flag DoH per browser. To restore flow visibility, push the Disable DoH policy from Endpoints → Setup.
Diagnosing a whole fleet
Waxell support can give you a read-only fleet diagnostic script to run as SYSTEM from your RMM or MDM. It prints one line per machine — enrollment, credentials, browser bridge, capture, last upload, recent crashes — and is the fastest way to find the outliers in a large rollout.
Reporting a problem
Send Waxell support the device name from the Health page, the time it happened, the relevant log (above), and a screenshot of anything in the console that looks wrong.