> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postqueen.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> Where to find help with PostQueen, and how to write a report that gets a fast answer

Something is not working and you want a person to look at it. Here is where to go.

<CardGroup cols={2}>
  <Card title="GitHub Issues" icon="github" href="https://github.com/GkhanKINAY/postqueen-app/issues/new/choose">
    Something is broken: a bug, an error, a crash. Screenshots and logs attached
  </Card>

  <Card title="Email" icon="envelope" href="mailto:support@postqueen.ai">
    Billing, your account, and anything you would not post publicly
  </Card>
</CardGroup>

## What is covered where

|                              | Self-hosted                                                                               | PostQueen Cloud |
| ---------------------------- | ----------------------------------------------------------------------------------------- | --------------- |
| **A bug, an error, a crash** | Yes. Open a [GitHub issue](https://github.com/GkhanKINAY/postqueen-app/issues/new/choose) | Yes             |
| **"How do I do X?"**         | Not covered                                                                               | Yes             |
| **Billing and your account** | Nothing to bill                                                                           | Email support   |

<Info>
  **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.
</Info>

## Check these first

Most reports match one of these in a minute.

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="wrench" href="/troubleshooting/overview">
    Sorted by symptom
  </Card>

  <Card title="When a post fails" icon="triangle-exclamation" href="/troubleshooting/post-failed">
    The most common report, and how to tell the three causes apart
  </Card>

  <Card title="Known issues" icon="bug" href="/troubleshooting/known-issues">
    Bugs we have already confirmed, with workarounds
  </Card>

  <Card title="FAQ" icon="circle-question" href="/faq">
    The questions that come up most
  </Card>
</CardGroup>

## 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.

<AccordionGroup>
  <Accordion title="Goal — what you wanted to happen" icon="bullseye">
    * *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*
  </Accordion>

  <Accordion title="Environment — browser, OS, install" icon="desktop">
    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*
  </Accordion>

  <Accordion title="Changes — what moved before it broke" icon="clock-rotate-left">
    * *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 …*
  </Accordion>

  <Accordion title="Results — what you saw instead" icon="eye">
    * *I see a blank screen*
    * *I see an error message*
    * *I see a 404 page*
  </Accordion>
</AccordionGroup>

## Billing, refunds and your account

Write to [support@postqueen.ai](mailto:support@postqueen.ai) from the address on your account, and
say what you expected against what happened instead. Closing the account or making a GDPR request
goes to the same address; there is no self-serve delete button in the app today.

<Warning>
  Leave API keys, OAuth secrets and card numbers out of the message. We do not need any of them to
  help you.
</Warning>

Many *"I was charged but…"* cases turn out to be a script blocker stopping Stripe.js, or a private
window throwing localStorage away: [billing troubleshooting](/troubleshooting/billing).