Troubleshooting

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

Common Issues & Solutions

1. Authentication Errors (401 Unauthorized)

  • 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)

  • 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)

  • 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)

  • Cause: Server-side problems or unexpected errors.

  • Fix:

    • Retry the request after a short delay.

    • Check if the issue persists; if yes, contact Testra support with error details.

5. Invalid Input or Request Schema (422 Unprocessable Entity)

  • 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

  • Use the Testra 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 Testra dashboard to confirm uptime.

  • Logging & Monitoring: Enable /log endpoints on your servers for detailed tracing if available.

  • Community & Support: Join Testra’s Discord or contact support if you need help with complex issues.

PreviousExamplesNextTeam

Last updated