> For the complete documentation index, see [llms.txt](https://docs.tairon.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tairon.ai/tairon/troubleshooting.md).

# Troubleshooting

Use this guide to quickly identify and fix common problems when working with Tairon MCP servers and APIs.

***

### Common Issues & Solutions <a href="#common-issues-and-solutions" id="common-issues-and-solutions"></a>

#### **1. Authentication Errors (`401 Unauthorized`)** <a href="#id-1.-authentication-errors-401-unauthorized" id="id-1.-authentication-errors-401-unauthorized"></a>

* **Cause:** Missing or invalid API key in the `Authorization` header.
* **Fix:**
  * Verify your API key is correct and active.
  * Include header: `Authorization: Bearer YOUR_API_KEY`.
  * Do not expose API keys in client-side code.

***

#### **2. Server Not Found (`404 Not Found`)** <a href="#id-2.-server-not-found-404-not-found" id="id-2.-server-not-found-404-not-found"></a>

* **Cause:** Incorrect server ID or endpoint URL.
* **Fix:**
  * Double-check the server ID used in your API call matches the directory.
  * Ensure you’re calling the correct endpoint URL (e.g., `/servers/{serverId}`).

***

#### **3. Rate Limit Exceeded (`429 Too Many Requests`)** <a href="#id-3.-rate-limit-exceeded-429-too-many-requests" id="id-3.-rate-limit-exceeded-429-too-many-requests"></a>

* **Cause:** You’ve sent more requests than your plan allows.
* **Fix:**
  * Review your API usage in your dashboard.
  * Upgrade your plan if needed.
  * Implement exponential backoff or retries in your client.

***

#### **4. Internal Server Error (`500 Internal Server Error`)** <a href="#id-4.-internal-server-error-500-internal-server-error" id="id-4.-internal-server-error-500-internal-server-error"></a>

* **Cause:** Server-side problems or unexpected errors.
* **Fix:**
  * Retry the request after a short delay.
  * Check if the issue persists; if yes, contact Tairon support with error details.

***

#### **5. Invalid Input or Request Schema (`422 Unprocessable Entity`)** <a href="#id-5.-invalid-input-or-request-schema-422-unprocessable-entity" id="id-5.-invalid-input-or-request-schema-422-unprocessable-entity"></a>

* **Cause:** Request payload does not match expected format.
* **Fix:**
  * Verify JSON structure and required fields in your request body.
  * Use the MCP Inspector to test requests interactively.

***

#### Additional Tips <a href="#additional-tips" id="additional-tips"></a>

* **Use the Tairon Inspector:** The Inspector lets you test servers live and view request/response details. It’s invaluable for debugging.
* **Check Server Status:** Some errors might result from server downtime. Use `/health` endpoints or Tairon dashboard to confirm uptime.
* **Logging & Monitoring:** Enable `/log` endpoints on your servers for detailed tracing if available.
* **Community & Support:** Join Tairon’s Telegram or contact support if you need help with complex issues.