LLMtoMD logoLLMtoMD
All docs

Troubleshooting

Troubleshooting

Fixes for the common issues — auth errors, the VS Code sign-in loop, out-of-credits, slow conversions, and rejected uploads.

Most problems fall into a handful of categories. Here's how to diagnose and fix each.

"Connection key is missing, invalid, or revoked" (401)

Your agent isn't authenticating.

  • Open Settings → Connect to Claude, generate a new connection key, and update it in your connector config (the X-API-Key header or OAuth login).
  • Make sure you copied the whole key, including the mic_ prefix.
  • If you regenerated the key, the old one stops working — update every client that used it.

VS Code keeps looping on the sign-in prompt

VS Code (and some strict OAuth clients) key their session on the exact issuer string. If you're stuck in a repeating "wants to authenticate" loop:

  • This is resolved on our side — the server now advertises a consistent issuer.
  • Fix locally by removing and re-adding the MCP server, then signing in once more. In the Command Palette: MCP: Reset/Clear Authentication for the LLMtoMD server, then reconnect.
  • Confirm your .vscode/mcp.json uses https://mcp.llmtomd.com/mcp exactly.

"You're out of LLMtoMD credits" (402)

Conversions consume credits.

  • Top up on the billing page, then retry.
  • Reading, searching, and asking are cheap or free — if you're burning credits fast, it's conversions (especially crawling whole sites or large files).
  • Credits roll over and don't reset monthly, so a top-up isn't use-it-or-lose-it.

"Rate limit reached" (429)

You've sent too many requests in a short window. Wait a minute and try again. If you're scripting against the REST API, add a small delay between requests.

A conversion seems stuck

Large or slow sources (big PDFs, long audio, whole sites) may not finish within the agent's wait window. The agent gets a "still processing" handle — the document appears in list_documents shortly after. Just ask:

Is my conversion done yet? List my recent documents.

"Storage rejected the upload"

When uploading a local file via a presigned URL, the PUT must send the same Content-Type the upload was reserved with. If you're scripting it by hand, make sure the -H "Content-Type: …" on the PUT matches what you passed to POST /uploads. Presigned URLs also expire (about 15 minutes) — reserve a fresh one if it's been a while.

"This account doesn't have access" in the dashboard

Some actions (like editing another account's credits) require elevated platform access. Standard accounts manage their own library and billing; org-level and platform-admin actions are gated separately.

Still stuck?

Email support@llmtomd.com with what you were doing, the client (Claude/Cursor/VS Code/ChatGPT), and any error text. Include the approximate time so we can match it to logs.

Related