Appearance
Runbook
You're here because something is broken, or you're proactively hardening / responding to a security situation. Pick the page that matches your need.
Security
| Need | Page |
|---|---|
| Restrict admin port (2087) access to specific IPs | security/admin-ip-allowlist.md |
| Take the panel offline urgently while keeping hosting running | security/panel-kill-switch.md |
| Lock the entire server down for forensic investigation | security/emergency-lockdown.md |
| Suspected compromise — what to do | security/post-compromise-checklist.md |
The security pages also reference docs/admin/security.md, which describes the EasyCP security model end-to-end (trust boundaries, controls, what's defended, what isn't).
Privilege separation
| Need | Page |
|---|---|
| How the panel and the WordPress daemon run de-rooted behind the root broker, and how to read the status | privilege-separation.md |
This is the companion to the in-panel Privilege Separation page.
If your symptom doesn't match any of these, the runbook doesn't yet cover it. File an issue so it gets added.
How to read these pages
Every page has the same shape:
- Symptom — what you're seeing. If it doesn't match what you're seeing, you're on the wrong page.
- Assessment — what to verify before running any commands. Skipping this step turns small problems into big ones.
- Procedure — numbered steps. Each has a command (or UI action) and an expected outcome. If the outcome differs, the page calls out where to branch.
- Verification — how you know the problem is fixed.
Read the whole page once before running anything. The procedures don't make sense out of order.
Conventions
- Commands are shown without prompts (
$or#) so they paste cleanly. Run them as root unless the page says otherwise. - File paths are real paths on a default install. Adjust if you've customised.
- "The panel" means the EasyCP main panel API server.