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

# Troubleshooting

Find a fix by symptom.

## Check the state first

Run expl server status. Exit code 0 from expl server tools list does not mean that the connection works (see [Inspect commands](https://docs.exploratory.io/en/cli/server/commands.md#inspect-list)). To see what is sent and received, add `--verbose`; it prints to standard error. Tokens are never printed, but review the output before you paste it anywhere.

## When you contact support

Send these to [support@exploratory.io](mailto:support@exploratory.io): the output of `expl --version`, the command you ran, the exit code and the message. Hide any token or API key.

## When you cannot connect from a company network

Ask your IT administrator to allow communication with exploratory.io. For an on-premises server, ask them to allow the URL of your own server.

## The command is not found

| What you see | What to do |
| - | - |
| expl: command not found | Open a new terminal and run it again. The expl that comes with Desktop is added to your PATH when the app starts. |
| npm install -g stops with EEXIST | Do not run it again with `--force`: that replaces the expl that comes with Desktop. |
| You do not know which expl runs | Run which -a expl (where expl on Windows) to see every copy. |

For how to check when two copies are installed, see [Installation](https://docs.exploratory.io/en/cli/server/install.md).

## Sign-in

| What you see | What to do |
| - | - |
| `Run "expl server login".` | You are not signed in, or the saved login was rejected. Run expl server login. |
| The API key is invalid or expired. Create a new one in Account Settings > API Keys. (UNAUTHORIZED) | The key is wrong, expired or revoked. Create a new API key, then set EXPL\_SERVER\_TOKEN or run `expl server login --with-token`. Exit code 4. |
| API keys are disabled by your administrator. / This IP address is not allowed for API keys. | An administrator turned API keys off or limits them to certain IP addresses. Ask your administrator, or sign in with expl server login. Exit code 4. |
| `--token` was removed. … | Set EXPL\_SERVER\_TOKEN, or run `expl server login --with-token`. Exit code 2. |
| Too many failed API key attempts. Try again later. | Many refused keys came from this address in a short time. Fix the key and try again later. |
| The redirect URL has no authorization code. | With `--no-browser`, you pasted the first URL. Paste the redirect URL that starts with [http://127.0.0.1/callback?code=](http://127.0.0.1/callback?code=) instead. |
| Exit code 4 (Desktop) | See the code at the end of the message in [Exit codes and errors](https://docs.exploratory.io/en/cli/server/exit-codes.md#action): NOT\_SIGNED\_IN, UNAUTHORIZED, PAIRING\_REQUIRED, CHANNEL\_DISABLED or PERMISSION\_DENIED. |

To switch to a saved login while EXPL\_SERVER\_TOKEN is set, run unset EXPL\_SERVER\_TOKEN first, because it is used before a saved login.

For how to create, pass and revoke an API key, see [API keys](https://docs.exploratory.io/en/cli/server/token.md).

## Connection

| What you see | What to do |
| - | - |
| Exit code 3 (Server) | The server cannot be reached. Check the network and run it again. |
| Exit code 3 (Desktop) | Start Exploratory Desktop and run it again. |
| A message names a tool, such as chart\_query | Run expl server tools describe \<tool\_name> to see the command for that tool. |
| Odd results | Add `--verbose` to see what is sent and received. Review the output before you paste it anywhere. |

## Limits

| What you see | What to do |
| - | - |
| Too big: expected number to be \<=50 at limit | Set `--limit` of search to 50 or less. |
| has\_more is true and not everything came back | For search and dataframe preview, get the next page with `--offset`. For dataset query, narrow the query or aggregate. |
| SERVER\_BUSY | Another export is running, or you reached the hourly export limit. Try again in a few seconds; for the hourly limit, wait up to an hour. |

The server that returns these errors is the same one that MCP Server uses. For the other errors it returns (NOT\_FOUND, PERSONALIZED\_CONTENT, CONTENT\_UPDATING, UNSUPPORTED\_OPERATION, RESULT\_TOO\_LARGE) and the limit on the number of requests per minute (120), see [Limits and errors](https://docs.exploratory.io/en/mcp/server/limits.md#errors) of MCP Server.

## Data that cannot be queried

| What you see | What to do |
| - | - |
| DATASET\_UNAVAILABLE | The publisher needs to republish it from the latest version of Exploratory Desktop. |
| DATA\_EGRESS\_LIMIT | The publisher does not allow downloading this data as a file. Use fetch or dataframe get-schema for what the publisher shares. |
| Unknown property "by" in a sort entry. (INVALID\_SORT) | In sort, name the output column with field. |

For how to write the JSON arguments, see [Query data](https://docs.exploratory.io/en/cli/server/guides/query-data.md#json).


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