GitHub Issues
Something is broken: a bug, an error, a crash. Screenshots and logs attached
Billing, your account, and anything you would not post publicly
What is covered where
Self-hosting is supported for defects, not for usage. Find a bug and it goes on the issue
tracker like any other: it gets read, and fixing it helps everyone running the same code. Working
out how to do something with the product is a different job, and that is what a Cloud subscription
pays for.There is no promised reply time on issues. Write the detail down while it is fresh.
Check these first
Most reports match one of these in a minute.Troubleshooting
Sorted by symptom
When a post fails
The most common report, and how to tell the three causes apart
Known issues
Bugs we have already confirmed, with workarounds
FAQ
The questions that come up most
What to put in the report
Four short answers are usually all it takes. Cover them and the maintainer who opens your issue can go straight to the fix, instead of spending the first reply asking which browser you are on.Goal — what you wanted to happen
Goal — what you wanted to happen
- I want to schedule a post on Reddit at 6pm
- I want to run in a Linux container on a Raspberry Pi
- I want to use a custom domain name
Environment — browser, OS, install
Environment — browser, OS, install
For trouble in the web app the browser is what matters. For an install, your OS and how you installed it.
- I am using Firefox on Windows 10
- I am using a Raspberry Pi 4 with Ubuntu 20.04, and Node version 18
- This is a fresh installation on a Mac
Changes — what moved before it broke
Changes — what moved before it broke
- I updated my browser to the latest version and now …
- I upgraded to the latest release and now …
- I think this used to work, but now …
Results — what you saw instead
Results — what you saw instead
- I see a blank screen
- I see an error message
- I see a 404 page