> ## Documentation Index
> Fetch the complete documentation index at: https://frp.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# Operations Overview

> Choose the correct safe workflow for updates, backup/restore, diagnostics, lifecycle changes, and troubleshooting.

# Operations Overview

Use this page as the operator map after deployment.

```mermaid theme={null}
flowchart TD
    A[Need to operate or fix something] --> B{What is the goal?}
    B -->|Check health| D[Diagnostics / doctor]
    B -->|Install newer project build| U[Updates]
    B -->|Protect or recover state| R[Backup & Restore]
    B -->|Stop / remove / block something| L[Lifecycle Semantics]
    B -->|Something is broken| T[Troubleshooting]
```

<CardGroup cols={2}>
  <Card title="Diagnostics" icon="stethoscope" href="/operations/diagnostics">
    Start with read-only status and `doctor` before changing generated state.
  </Card>

  <Card title="Updates" icon="arrows-rotate" href="/operations/updates">
    Update the project or pinned FRP without intentionally losing identity, CA, token, or ports.
  </Card>

  <Card title="Backup & Restore" icon="box-archive" href="/operations/backup-restore">
    Protect and recover trust, registry, configuration, and port reservations.
  </Card>

  <Card title="Lifecycle" icon="diagram-project" href="/operations/lifecycle">
    Choose disable, revoke, release, uninstall, or another operation without confusing their effects.
  </Card>

  <Card title="Troubleshooting" icon="triangle-exclamation" href="/troubleshooting/overview">
    Follow a symptom-driven decision tree for enrollment, tunnel, port, DNS, and certificate problems.
  </Card>

  <Card title="Release Status" icon="tag" href="/reference/release-status">
    Distinguish stable v2.1.2 from the 2.1.3 development branch.
  </Card>
</CardGroup>

## Safe operating sequence

```mermaid theme={null}
flowchart LR
    O[Observe] --> S[Show status / info]
    S --> D[Run doctor]
    D --> B{Need state change?}
    B -->|No| E[Stop / collect evidence]
    B -->|Yes| K[Create backup when appropriate]
    K --> C[Make documented change]
    C --> V[Verify status + doctor + service path]
```

## State FRP Auto Deploy tries to preserve

Normal supported updates and reboots are designed to preserve:

* CLIENT ID and management identity
* project private CA
* FRP token
* server registry
* service definitions
* persistent public-port reservations

## Avoid destructive debugging

Do not begin troubleshooting by manually editing:

```text theme={null}
/etc/frp/frps.toml
/etc/frp/frpc.toml
/var/lib/frp-auto-deploy/registry.json
/etc/frp/client-state.json
management identity / PKI files
```

Use `frpctl doctor` first and follow the documented lifecycle command for the actual intent.

<Tip>
  If you are unsure whether you mean **disable**, **revoke**, or **release**, read [Lifecycle Semantics](/operations/lifecycle) before executing the command.
</Tip>