Doctor, Health, support bundles, and logs

Doctor is read-only

omakase plus doctor checks the selected installation without creating a category, library, file, or database row.

Depending on the mode, it checks:

• data, import, and library directories;
• permissions, capacity, and filesystem behavior;
• SQLite integrity and migrations;
• ffprobe availability;
• Plex reachability and library mapping;
• provider reachability;
• qBittorrent scope and VPN posture;
• selected profile consistency.

Each failure includes a stable reason code and a remediation written for an operator.

Run the smallest relevant check

For import-only:

omakase plus doctor \
  --data-dir /srv/omakase/data \
  --import-root /srv/omakase/import \
  --library-root /srv/omakase/library \
  --acquisition-mode import-only \
  --vpn-mode none \
  --plex-url http://127.0.0.1:32400

Add provider or VPN options only when that lane is intentionally enabled.

Health in the interface

Health translates live checks and recent receipts into owner language. It distinguishes:

• ready;
• some sources unavailable;
• waiting for the next scheduled check;
• an incomplete title with an explicit missing count;
• a configuration or provider action that needs attention.

A partial catalog outage does not erase successful source results. A healthy container does not override a failed Plex or media readiness check.

Build a support bundle

Use the same Doctor options to create a shareable diagnostic:

omakase plus support-bundle \
  --output ./omakase-support.zip \
  <same Doctor options>

The default bundle excludes:

• SQLite databases;
• credentials and tokens;
• magnets and tracker URLs;
• full filenames and private paths;
• watch history.

Paths and names that appear in included logs are replaced with short hashes.

Logs without credential leakage

Prefer application receipts and bounded container logs. Before sharing:

1. use the support-bundle command;
2. inspect the archive manifest;
3. confirm no .env or secret file is present;
4. avoid screenshots of browser developer tools or private settings;
5. never paste provider headers, OAuth callbacks, or full request URLs.

A useful diagnostic sequence

1. Record the exact release revision.
2. Run Doctor.
3. Read Health and the latest activity receipt.
4. Confirm mounts and file reads.
5. Confirm Plex mapping.
6. Reproduce one representative failure.
7. Build the support bundle.
8. Back up before any repair.

Continue with plain-language troubleshooting.