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

# Diagnosing a problem

> Work from what you observe to the page that fixes it.

Start from what you can see. Each row below leads to one page.

## Start with the console

Almost every problem names itself in the server console at start. Find the **first** line mentioning
`element_sdk` or the product (the lines below it are usually consequences) and look it up in
[Console messages](/support/console-messages).

If the console says nothing about the product at all, the server never found the resource. Go
straight to [A product does not start](/support/product-will-not-start).

## By symptom

<CardGroup cols={2}>
  <Card title="The product fails at start, or never appears" icon="circle-xmark" href="/support/product-will-not-start">
    A product does not start.
  </Card>

  <Card title="A setting you edited changes nothing" icon="sliders" href="/support/configuration-not-applied">
    Configuration changes have no effect.
  </Card>

  <Card title="Wrong language, untranslated strings, or a key name on screen" icon="language" href="/support/text-is-wrong-or-missing">
    Text is wrong or missing.
  </Card>

  <Card title="A console message you do not recognise" icon="terminal" href="/support/console-messages">
    Console messages.
  </Card>

  <Card title="Something works differently after an update" icon="arrows-rotate" href="/getting-started/updating">
    Update a product or the SDK.
  </Card>

  <Card title="A problem specific to one product" icon="box-open">
    That product's own troubleshooting pages.
  </Card>
</CardGroup>

## Before you report a problem

Check these three first. They resolve most reports without a ticket.

1. **Restart, and read the start-up output.** Configuration, language files and the choice of which
   of your resources a product uses are all decided at start.
2. **Confirm the versions match.** The product states which SDK versions it accepts, and refuses to
   start outside them. See [SDK version requirements](/sdk/compatibility).
3. **Undo your last edit.** Restore the file the release shipped and confirm the problem goes away.
   That separates a product fault from a configuration fault, which is the first thing support will
   ask.

If the problem survives all three, [get in touch](/support/contact).