Found a bug?
Help us fix it.
NinerLog is built by pilots, for pilots — and we rely on your reports to keep it sharp. Every bug you tell us about helps the whole community.
Open a GitHub issue.
All NinerLog bug reports — whether they affect the API, the web app, the mobile PWA, the self-hosted Docker images, or the website — are tracked in a single place: the ninerlog-api issue tracker on GitHub.
We do this on purpose: one tracker means nothing falls through the cracks, and the maintainer can prioritise across the whole stack at a glance.
Tip: please search existing issues first — someone may have already squawked the same thing.
What to include in your report.
Good bug reports get fixed faster. A great one reads like a NOTAM — clear, precise, and actionable.
What happened
A short description of the actual behaviour you observed — the more specific, the better.
What you expected
What did you think would happen instead? This helps us tell bugs apart from feature requests.
Steps to reproduce
Numbered steps that reliably trigger the bug. If you can’t reproduce it, tell us that too.
Environment
Browser & version, operating system, mobile or desktop, and whether you’re on app.ninerlog.com or self-hosted.
Screenshots / logs
A picture is worth a thousand stack traces. Browser console errors are pure gold.
When it started
Has it always been like this, or did it appear after a recent update? Approximate dates are fine.
Please don’t include personal data — full names, dates of birth, license numbers, or full flight records. A redacted screenshot is always better than a real one.
Email us instead.
GitHub is the fastest path — you’ll get notified when the bug is triaged, fixed, and shipped. But if you don’t have an account and don’t want to create one, that’s completely fine.
Send the same information (what happened, what you expected, steps to reproduce, environment, screenshots) to:
We’ll create a GitHub issue on your behalf and reply with the link so you can follow along.
Found a security issue?
Please do not open a public GitHub issue for security vulnerabilities. Email hej@ninerlog.com directly, or follow the disclosure process in our SECURITY.md.