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

# Get help

> Where to ask for help, and what to send so the first reply can answer it.

Support happens in tickets on our Discord server. Before you open one,
[Diagnose a problem](https://docs.elementlabs.net/troubleshooting/index.md) covers the causes behind most tickets, and its checks
are the first ones we would ask you to run.

> **[Open a ticket on Discord](https://discord.gg/elementlabs)**
>
> discord.gg/elementlabs

## What to send

A ticket with these can usually be answered in the first reply:

| What | Where to find it |
| - | - |
| The product and its version | The `version` line in the product's `fxmanifest.lua`. |
| Your `element_sdk` version | The `version` line in `element_sdk/fxmanifest.lua`. |
| The console output around the problem, as text | From a few lines before the first error to a few after. The line that names the cause is often above the one that looks like the problem. |
| What you changed last | A setting, a language file, an update, or a resource you added. |
| Your Tebex transaction ID | In the purchases on our shop, and in the Tebex receipt email. |

Also tell us:

* what you expected and what happened instead;
* whether it still happens with the files the release shipped in place of your own. That one test
  separates a product fault from a configuration problem;
* whether it happens for every player or only some.

## What never to send

Your server license key, database passwords, and any webhook or API key from your own settings. We
never need them and will never ask for them. Check a configuration file for your own secrets before
you attach it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.