> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.janitorai.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Chutes Error Guide

# Chutes Proxy Error Guide
Even when you’ve got your config right, Chutes can spit out strange error messages that don’t explain much. This guide breaks those down and tells you exactly what went wrong, and how to fix it without wasting hours guessing.
---
# Fix-It First: Proxy Error Basics
Before you worry about what the error message says, take a second to make sure your setup isn’t just... being fussy. 
**Step 1:** Open your config and check if it says Active. If it doesn’t, click to activate it. 
**Step 2:** Now hit Save Settings, yes, even if you didn’t change anything. 
**Step 3:** Then refresh the entire Janitor.AI page. **Step 4:** Once you’re back in, re-open your config and click `Test`.
If things still aren’t working, that’s when it’s time to match your error message to the quick guide below.
---
# Proxy Errors

### **“Invalid Token” (401)**
Your Chutes API key is wrong. 
**Fix:** Double-check that the key starts with `cpk_`. No extra spaces or invisible characters. Paste it directly into your config.

### **“model not found [model]” (404)**
The model name you entered doesn’t exist or is typed wrong.
**Fix:** Copy a valid model name from [Chutes](https://chutes.ai/app). Click the API tab under a model to copy its correct name. Common working names: `deepseek-ai/DeepSeek-R1` `deepseek-ai/DeepSeek-V3-0324`

### **“No matching cord found!” (404)** 
Your API URL is wrong. 
**Fix:** Use this exact URL: `https://llm.chutes.ai/v1/chat/completions` No extra slashes, no spaces. It must match exactly. 

### **“exhausted all available targets to no available” (500)** 
Chutes’ servers are down or unreachable.
**Fix:** There’s nothing you can do. Wait it out, the provider has to fix this one. You can check the [Chutes Uptime page](https://status.llm.chutes.ai/) (not always accurate). Specific ones for [Deepseek R1 free](https://openrouter.ai/deepseek/deepseek-r1:free/uptime) and [Deepseek V3 free](https://openrouter.ai/deepseek/deepseek-chat:free/uptime) are on [OpenRouter](https://openrouter.ai/)

### **“No instances available (yet) for chute_id=” (503)**
The model is currently overloaded or restarting. 
**Fix:** Just wait a few minutes. It usually comes back online shortly.