Skip to main content

Troubleshooting method

1. Preserve the exact evidence​

Copy the complete error message, timestamp, Jiandu version, command or browser action, and the last known successful operation. Redact tokens, cookies, passwords, document contents, and private URLs before sharing.

2. Identify the boundary​

Ask which layer first failed:

  • browser to HTTPS proxy;
  • proxy to Jiandu;
  • Jiandu to database or blob storage;
  • capture/email connector to Jiandu;
  • backup or migration tool to its destination.

Test that boundary directly using a non-sensitive request. Avoid changing several layers at once.

3. Search the stable message​

Use the site's search with the exact phrase, including messages such as another Jiandu process is already using this installation. The error message reference maps stable messages to likely causes and safe next actions.

4. Protect the current state​

Before repair, snapshot or copy the database, blobs, configuration, and relevant logs. Never restore, migrate, or delete over the only copy.

5. Make one reversible change​

Validate configuration, restart once, and repeat the same observation. If it does not help, revert before testing the next hypothesis.

When requesting help, include the evidence from step 1 and the result of each narrow test—not a secret-filled configuration dump.