Installation and Version Checks
Run a Self-check
- Enter the admin panel as a super administrator.
- Open Installation & Maintenance at the bottom of the sidebar.
- Start a check and inspect each result.
- For troubleshooting, export the JSON report and provide it with deployment logs.
The page checks D1 connectivity, migration records, tables/columns/indexes/triggers, session KV, optional R2, all six Durable Objects, and required environment variables. Reports exclude secret values. Demo results are simulated.
Checks are read-only and do not migrate, clear data, or run GC. Afterward, test sign-in, messages, and attachments to confirm the application works.
Handle Failed Checks
| Result | Next step |
|---|---|
| Missing migrations or structure | Inspect 00 Deploy Worker logs and follow D1 Migrations |
| KV or D1 unavailable | Check Cloudflare bindings and service status |
| R2 not bound | Follow Attachments and Storage and redeploy |
| Missing environment variable | Review Site Configuration and related Secrets |
Structure and environment checks confirm existence. Verify writes, decryption, and scheduled delivery through functional tests. If sign-in is unavailable, inspect Cloudflare and Actions logs directly.
Check for Version Updates
Open the version update section under Site appearance and click Check for updates. The browser compares the deployment commit with the GitHub branch. Follow Update an Existing Site to apply updates.
Actions records the repository, branch, and SHA automatically. For manual deployments, build from a clean Git commit that has been pushed.
The check needs a public GitHub repository and anonymous API quota. Private repositories, unpushed commits, or API rate limits can make an accurate check unavailable.
View Storage Usage
Open Storage statistics to view the saved snapshot. Administrators with scan permission can scan usage by user, Telegram, and unknown source. Scans have page and frequency limits and make R2 list requests.