Janitor AI Login _ Sign Up, JanitorLLM Setup and Fixes

Published November 20, 2026

How to Fix Janitor AI API Errors _ Network Error, 401, 402, 429

Your chat worked yesterday. Today every message dies with a network error, and nothing about your setup changed. This is the most common Janitor AI complaint there is, and the message is misleading. The fault is almost never your internet. It sits in the link between Janitor and the model provider you connected, and each error code points at a different layer of that link.

Work through this page in order. Most setups are fixed inside five minutes once you check the right layer first instead of restarting your router.

First, the 60-second test

Before you change anything, find out which layer is broken. Switch your provider back to JanitorLLM in your model settings and send a short test message in a fresh chat. If JLLM answers, Janitor itself is fine and your account is fine. The problem is your proxy setup or your provider, full stop. If JLLM also fails, try a private browser window. Still dead? That is a platform or browser issue, not your key.

This one test saves most people an hour. Do not skip it.

The network error that is really a bill

Here is the trap. When your OpenRouter or DeepSeek balance hits zero, the provider answers with a 402, which means insufficient balance. Janitor flattens that into a plain "network error" on your screen. You blame your Wi-Fi, swap browsers, restart everything, and nothing changes, because the fix was adding a few dollars of credit.

The tell is timing. Chats that die overnight with no settings change are a balance problem until proven otherwise. Check your provider balance before you touch a single setting.

Error codes, decoded

401 — the key. The key is missing, wrong, expired, or pasted badly. Copy it fresh from your provider and paste only the key, with no space at either end and nothing typed in front of it. Phone copy-paste loves adding a stray space. Also check the key is saved under the same proxy configuration your chat is actually using. Still failing? Generate a new key and replace it.

402 — the money. Your balance or billing authorisation ran out. Top up, or check that your card on file still works.

403 — permission. The key exists but is not allowed to do what you asked. That can be a model your account cannot use, a region limit, or a provider rule. Check the model is open to your account tier.

404 — the address. Either the proxy URL is wrong or the model ID is. Janitor wants the full chat-completions URL, for OpenRouter that is https://openrouter.ai/api/v1/chat/completions. For the model, copy the exact ID from the provider's current model list. Free model IDs get retired, and a ":free" ID that left the list returns a 404.

429 — the limit. Too many requests. On free models this is the daily cap, and here is the nasty part: failed requests can still count against it, so hammering regenerate on a broken bot burns your allowance fast. Wait 10 to 15 minutes, switch to a different model, or use your own paid key. Our full proxy explainer covers how the caps differ per provider.

500 to 504 — their side. The provider or Janitor is down or overloaded. There is no setting that fixes this. Wait it out and try again later.

The mismatch nobody checks

The proxy URL, the API key, and the model name must all belong to the same provider. A DeepSeek key next to an OpenRouter URL fails every single time, usually as a 401 hiding inside a network error. When you switch providers, change all three fields together, save, and reload the chat if the site asks you to. Janitor can also cache an old setting, so if a fix "did nothing," reload the page and send a fresh test before you change anything else.

When it is not the API at all

A few failures wear the same clothes. "Error getting characters" means the character search service is struggling on Janitor's side; wait it out. A chat that freezes or goes dull after hundreds of messages is usually a full context window, not an error: start a new chat and paste a short recap. Login loops are browser problems nine times out of ten, so clear cookies for the site or use a private window.

And a safety note that belongs in every error guide: never share your key while asking for help. Not in a screenshot, not in a Discord message, not in a comment here. If your key has been visible anywhere public, revoke it and make a new one before you do anything else. The login and setup walkthrough on our homepage shows where keys live in the current settings screens, so you can check yours against it.

Run the JLLM test, read the code, fix that one layer. That order solves nearly every broken Janitor chat you will ever meet.