Skip to main content

​
Operations Overview

Use this page as the operator map after deployment.

Diagnostics

Start with read-only status and doctor before changing generated state.

Updates

Update the project or pinned FRP without intentionally losing identity, CA, token, or ports.

Backup & Restore

Protect and recover trust, registry, configuration, and port reservations.

Lifecycle

Choose disable, revoke, release, uninstall, or another operation without confusing their effects.

Troubleshooting

Follow a symptom-driven decision tree for enrollment, tunnel, port, DNS, and certificate problems.

Release Status

Distinguish stable v2.1.2 from the 2.1.3 development branch.

​
Safe operating sequence

​
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:
Use frpctl doctor first and follow the documented lifecycle command for the actual intent.
If you are unsure whether you mean disable, revoke, or release, read Lifecycle Semantics before executing the command.
Last modified on September 7, 2026