Getting help
Where to ask a question, report a bug or a security problem, and suggest an improvement
Before you ask
Most answers are already written down; a quick look often saves a round trip:
- Search this site with the search box at the top of every page.
- Look up the exact error message in Troubleshooting, and skim the FAQ.
- Check the server log (Settings, then Server log) and the Status page, which report most configuration problems.
- Check the Changelog: the problem may already be fixed in a newer release.
Where to go
Each kind of request has its own place, all on GitHub:
| You want to | Go to |
|---|---|
| Ask a question or share an idea | Discussions |
| Report a bug | New issue → Bug report |
| Suggest a feature | New issue → Feature request |
| Report a security problem | Report a vulnerability, privately |
| Fix or improve this documentation | Edit this page on GitHub at the bottom of any page, or an issue on the website |
Reporting a bug
A report that can be reproduced gets fixed fastest. The bug report template asks for the following:
- Version : shown under About in the help (?) menu of the top bar
- Deployment : Docker, Docker Compose, Kubernetes or from source
- Steps to reproduce : what you did, what you expected, and what happened instead
- Evidence : the relevant lines of the server log, and a screenshot when the problem is visible
For a problem with a form, include a minimal form definition that shows it. Remove passwords, tokens, host names and any other private data from logs and forms before you post them: issues and discussions are public.
Reporting a security problem
Never open a public issue for it: use Report a vulnerability, which only the maintainers see.
The security policy lists the supported versions and what happens after you report.