WordPress Plugin
Learn all the capabilities, admin screen and lifecycle of AnchorUptime Crash Shield.
Overview
AnchorUptime Crash Shield is a crash-first uptime integration for WordPress. It serves ownership verification file, gets hidden plugin token, opens heartbeat endpoint, forwards fatal reports and uses MU helper for maintenance mode.
- Ownership verification and panel connection
- Heartbeat endpoint and fatal error reporting
- Maintenance mode and verify shim
- Diagnostics, audit, metrics, incidents and token health panels
WP Admin Screen
The plugin interface is located under Settings > AnchorUptime Crash Shield. In the connected state, Site ID, masked token, panel URL and capability badges appear on the screen.
| Card | Content |
|---|---|
| Live Overview | Panel Reachability, Heartbeat and Token Health summaries. |
| Performance | response/uptime summary from the metrics endpoint. |
| SSL & Domain | SSL and domain expiry information if there is a paid plan. |
| Recent Incidents | The last incident logs. |
| Token Health | token-info output. |
| Maintenance Mode | Result of local maintenance toggle and panel sync. |
| Audit Log | API audit-log logging. |
| Connection Diagnostics | Panel, heartbeat, token and well-known controls. |
| Crash Center | Fatal timeline, MU helper and crash telemetry summary. |
Configurable Settings
The main data changed by the user in the plugin is the verification token and the connection status. There is no heartbeat frequency setting like check interval; the heartbeat probe is called by the panel at the plan interval.
| Option | Objective |
|---|---|
au_plugin_token |
Encrypted plugin token. |
au_site_id |
Linked site ID. |
au_capabilities |
Token capability list. |
au_panel_url |
Panel base URL is locked with status.anchoruptime.com in the prod environment. |
au_verification_token |
The ownership token served in the well-known file. |
au_maintenance_active |
Local maintenance flagi. |
Debug and Troubleshooting
The plugin includes its own diagnostic tools: Run diagnostics, Export debug and Crash Center cards. Telemetry logs are stored in a separate au_telemetry_logs table and redacted exports can be produced.
- If panel health fails, check the server's status.anchoruptime.com access, DNS and outbound HTTPS traffic.
- If Heartbeat fails, test the REST API path, security plugins and reverse proxy rules.
- If MU helper is missing, review wp-content/mu-plugins write permissions.
-
On the WordPress side, it is also useful for general PHP debugging to turn on
WP_DEBUG_LOG, but the plugin does not depend on it for its crash telemetry.
Plugin Removal
At deactivation time the main runtime MU helper is removed, but the verify shim is intentionally left. Thus the /.well-known/dk-uptime-verify path will continue to run for a while even if the plugin is deactivated.
During full uninstall the plugin options are deleted, the telemetry table is downgraded and both runtime MU helper and verify shim are removed. So ownership verification is also completely cleaned.