Support
Lunar Paper support runs through
GitHub Discussions in
the lunarpaper/lunarpaper repository. Search there first, because someone may
already have asked your question or reported the same problem.
Choose the right place
Section titled “Choose the right place”| To | Go to |
|---|---|
| Ask how to do something, or get unstuck | Help and support |
| Report something that is not working | Bug reports |
| Suggest an improvement | Feature requests |
Each category opens a short form to fill in. Maintainers can turn a confirmed bug report into an issue.
What to include
Section titled “What to include”- The Lunar Paper version. In Lunar Paper, Settings > About shows it.
For a self-hosted installation, it is also the
LUNAR_PAPER_VERSIONsetting. - How you installed it, for example with Docker Compose,
docker run, Caddy for HTTPS or Arcane. - What you did, what happened, and what you expected instead.
- Any error message, and the relevant lines from Lunar Paper’s log:
docker compose logs lunarpaper, ordocker logs lunarpaperfor adocker runinstallation.
Keep private details out
Section titled “Keep private details out”Discussions are public. Never post your .env file, setup key, licence key,
passwords, API keys, database contents, or logs that contain any of them.
Remove names, email addresses and customer data from screenshots before you
attach them.
Report a security problem privately
Section titled “Report a security problem privately”Do not report a suspected vulnerability in Discussions. Email hello@lunarpaper.com with Security in the subject line. Include the affected version, what an attacker could do, and how to reproduce it, but no customer data or active credentials.
If a credential may have been exposed, revoke or change it straight away with the service that issued it. Do not send the exposed value to Lunar Paper.
