Help
Start with the symptom
If something is actually broken, go to Troubleshooting first. It is organised by symptom rather than by component, and every entry follows the same shape: Symptom → Diagnose (exact commands) → Root cause → Fix → Verify.
In this section
| Page | Use it when |
|---|---|
| FAQ | You have a question that starts with "can it…", "why does it…", or "should I…". |
| Glossary | A term in the docs is doing work you do not recognise — tconst, hardlink, Torznab, parking. |
Still stuck?
- Search — press Ctrl/⌘ + K. The whole site is indexed, and search runs offline.
- Check the reference — REST API, Permissions, and Environment Variables are generated from the source at build time, so they cannot be out of date.
- Open an issue — GitHub Issues. Include the diagnostics the troubleshooting page told you to gather; it is the difference between a one-reply answer and a week of back-and-forth.