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

# Diagnose a problem

> Start from what you see and reach the page that fixes it.

Start from what you see. Most problems name themselves in the server console when the product
starts, so read that first.

## Read the console first

Restart the product and find the **first** line that names it or `element_sdk`. The lines below it
are usually consequences. Look that line up in [Console messages](https://docs.elementlabs.net/troubleshooting/console-messages.md).

If the console says nothing at all about the product, the server never found it. Go to
[A product does not start](https://docs.elementlabs.net/troubleshooting/product-does-not-start.md).

## By what you see

> **[The product does not start](https://docs.elementlabs.net/troubleshooting/product-does-not-start.md)**
>
> An error at start, or no sign of the product at all.

> **[A setting has no effect](https://docs.elementlabs.net/troubleshooting/setting-has-no-effect.md)**
>
> You edited a file in `configs` and nothing changed.

> **[Text is wrong or missing](https://docs.elementlabs.net/troubleshooting/text-is-wrong.md)**
>
> The wrong language, a key name on screen, or a gap in a sentence.

> **[A script error with no file or line](https://docs.elementlabs.net/troubleshooting/script-errors.md)**
>
> `SCRIPT ERROR` with `?` where the file and line would be.

> **[A console line you do not recognise](https://docs.elementlabs.net/troubleshooting/console-messages.md)**
>
> Every message, what causes it and what to do.

> **[Something changed after an update](https://docs.elementlabs.net/get-started/update.md)**
>
> Settings back to defaults, or a renamed setting.

A problem with one product's own features is in the **Troubleshooting** group of that product's tab.

## Three checks that solve most problems

1. **Restart, and read the start.** Settings, languages and the resources a product uses are all
   decided when it starts.
2. **Check the versions.** The product's `INSTALL.md`, at the top of its download, says which `element_sdk` it needs. See
   [Versions and releases](https://docs.elementlabs.net/compatibility/versions.md).
3. **Undo your last change.** Put back the file the release shipped. If the problem goes away, the
   change was the cause. If it stays, it is not your configuration.

Still stuck? [Get help](https://docs.elementlabs.net/troubleshooting/get-help.md).


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