Skip to content
AI Dev Toolkit.
Esc
  • AI Token CounterCount tokens for GPT, Claude, Gemini, DeepSeek, Qwen and more.Tool
  • LLM API Cost CalculatorEstimate per-request, daily and monthly API costs.Tool
  • AI Model ComparisonCompare prices, context windows and features across models.Tool
  • AI Model Pricing PagesSpecs, real costs and cheaper alternatives for popular models.Tool
  • Context Window CheckerSee whether your text fits each model's context window.Tool
  • Subscription vs API CalculatorFind out whether a chat plan or the API is cheaper for you.Tool
  • GPU / VRAM CalculatorCheck how much VRAM a local model needs and which GPUs fit.Tool
  • Claude Code Error DatabaseExact Claude Code error messages with tested fixes.Tool

Coding Agents

Claude Code error database

Find the Claude Code error you’re seeing by its message or code, and fix it: certificate and proxy problems, rate limits, sign-in, model and install errors.

25 errors

Certificates and network (8)

Server and limits (5)

Sign-in (4)

Requests and models (4)

Install and setup (4)

Steps

How to use the claude code error database

  1. Copy the error from your terminal, or just the code in brackets such as UNABLE_TO_GET_ISSUER_CERT_LOCALLY.
  2. Paste it into the search box and open the matching error.
  3. Read what it means and check the causes that fit your situation.
  4. Work through the fixes in order; each one says how to confirm it worked.

Method

How it works

Claude Code’s error messages are short because they appear in a terminal. Each page here expands one of them: what actually went wrong, the situations that cause it, and the fixes in the order worth trying, with the exact commands for each operating system.

Where the most common errors come from

Most reports come from three places. Corporate networks that inspect HTTPS make Claude Code distrust the connection, which shows up as certificate errors with codes like UNABLE_TO_GET_ISSUER_CERT_LOCALLY or SELF_SIGNED_CERT_IN_CHAIN. Credentials cause the next group: an ANTHROPIC_API_KEY left in the environment quietly takes priority over a subscription login, leading to low rate limits, “credit balance is too low” or 401 errors. And busy periods produce temporary 500 and 529 errors that clear on their own.

How the pages are checked

Messages are matched against Anthropic’s error reference and the text inside the Claude Code 2.1.293 build, so the wording matches what you see. Fixes follow Anthropic’s documentation, rewritten with more context. Where a page says a step was tested, it was run on a real machine. Each page shows the date it was last verified and links its sources.

Some fixes need numbers from elsewhere on this site: the context window checker helps with “prompt is too long”, and the subscription vs API calculator helps decide whether a plan or the API suits your usage limits.

FAQ

Frequently asked questions

Why does Claude Code say “SSL certificate verification failed” at work but not at home?

Most company networks inspect HTTPS traffic with a proxy that re-signs it using the company’s own root certificate. Claude Code doesn’t trust that root unless it can read it from your operating system’s store or you point NODE_EXTRA_CA_CERTS at it. The UNABLE_TO_GET_ISSUER_CERT_LOCALLY page walks through exporting the certificate on Windows, macOS and Linux.

Is it safe to set NODE_TLS_REJECT_UNAUTHORIZED=0?

No. It turns off certificate checking for everything Claude Code does, so anyone on the network path could read or alter your traffic, including your API key and code. Trust the specific certificate your company uses instead.

What’s the difference between a 429 and a 529 error?

A 429 means you hit a rate limit for the key or project you’re using. A 529 means the API is at capacity for everyone; it doesn’t count against your usage, and switching to another model usually helps.

How were these fixes checked?

Every message is checked against Anthropic’s Claude Code error reference and the strings in the Claude Code 2.1.293 build, on 2026-10-08. Fixes follow Anthropic’s documentation, and steps marked as tested were run on a real machine, such as exporting a certificate on Windows and confirming Node loads it.

The message I see is slightly different. Is it the same error?

Probably. Claude Code reworded several messages between versions, and the same failure reads differently during /login, in -p mode or in the Desktop app. Each page lists the variants it covers, including older wordings. Search for the code in brackets, such as SELF_SIGNED_CERT_IN_CHAIN, if the wording doesn’t match.