Outlaw Panel documentation

Troubleshooting

Use evidence from health checks, systemd, PM2, Nginx, Prisma, and application logs.

Purpose

Restore service without guesswork or destructive shortcuts.

Step-by-step

  1. Identify the failing layer.
  2. Capture status and recent logs.
  3. Verify dependencies and configuration metadata without exposing secrets.
  4. Apply the smallest correction.
  5. Repeat the complete validation.
  6. Record the incident.

Example

Start with `systemctl --failed`, PM2 status, API health, and `nginx -t`.

Best practices

  • Preserve logs and rollback artifacts.
  • Use provider-console recovery when networking fails.

Troubleshooting

  • Do not delete data or regenerate keys to mask an error.
  • Escalate architecture and security decisions.

Related documentation

Backups and RecoveryInstallation