Troubleshooting
Confirm the scope first, then perform the smallest diagnostic. Do not use resetting data volumes, disabling security checks, or exposing internal ports as a "fix."
Basic health checks
bash
curl --fail --silent --show-error http://127.0.0.1:9090/ready
docker compose ps
docker compose logs web --tail 50Common symptoms
| Symptom | Check first | Next step |
|---|---|---|
| Cannot return to the application after sign-in | Public authentication origin, callback address, proxy headers | Correct the OIDC configuration, then sign in again |
| Cannot generate images | Subscription, job status, preset, and upstream health | Correct the configuration indicated by the page error |
| No purchasable plans | Billing connection, plan publication status, CNY price | Publish a valid plan, then reload the subscription page |
| Not enabled after payment | Notification verification, fulfillment status, billing queue | Wait for or repair fulfillment; do not enable it manually |
| Email not delivered | SMTP TLS, DNS, credential reference | Retest with a test mailbox and inspect delivery records |
Production domains and HTTPS
| Symptom | Check first | Next step |
|---|---|---|
| Domain resolves but HTTPS does not open | A record, 80/443 firewall, certificate issuance logs | In 1Panel, confirm the certificate domain and site root, then retry issuance |
| Home page works but deep documentation paths return 404 | Whether the static site root and build output are complete | Upload all contents of docs/.vitepress/dist and check rewrite rules |
| Callback address is not allowed after sign-in | Casdoor Application callback address | Use the exact https://app.jumpcli.com/api/identity/callback and sign in again |
| Return to HTTP or session expires after sign-in | PUBLIC_ORIGIN, HTTPS redirect, trusted proxy headers | Correct the public origin and proxy trust scope, clear test cookies, and retest |
| Subscription does not update after payment | HTTPS notification address, signature verification, Meteroid fulfillment | Keep the payment entry disabled; repair server-side notification and fulfillment, then retry with a test order |
When to escalate
For duplicate payments, permission errors, inconsistent billing invoices, audit-chain errors, data isolation issues, or secret leaks, immediately stop the related high-risk operations, retain the time, request ID, and security-log evidence, and hand the case to personnel with operator or deployment privileges.