12 UNIMPLEMENTED API Origin: Application & API Last updated 15 Oct 2026

gRPC Error: 12 UNIMPLEMENTED: unknown service x / Method not found

The server doesn’t have the service or method the client called — proto mismatch, wrong package name, or calling the wrong server.

Exact message you may see 12 UNIMPLEMENTEDunknown serviceMethod not found
Seen on: REST API

Meaning

Fully qualified names (package.Service/Method) must match exactly. Outdated generated code, missing service registration on the server, or routing through a proxy to the wrong backend cause it.

Common causes

  • Client and server proto definitions differ
  • Service not registered on the server
  • Wrong package/service name
  • Proxy routing to another service

⚡ Quick fix

  1. List services with grpcurl (reflection)
  2. Regenerate client stubs from the same proto
  3. Register the service in the server setup

Detailed fix by platform

Shell

  1. bash
    grpcurl -plaintext localhost:50051 list
    grpcurl -plaintext localhost:50051 describe orders.v1.OrderService

How to diagnose

  1. Services — Exposed list
  2. Protos — Same version?
  3. Routing — Correct backend?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

14 UNAVAILABLE — gRPC Error: 14 UNAVAILABLE: No connection established / failed to connect to all addresses (API)14 UNAVAILABLECannot GET — API Error: Cannot GET /api/... / No route matches / The route could not be found (API)Cannot GETconcurrent_requests_limit — API Error: Too many concurrent requests (concurrency limit reached) (API)concurrent_requests_l…CORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSDEADLINE_EXCEEDED — gRPC Error: 4 DEADLINE_EXCEEDED: Deadline exceeded (API)DEADLINE_EXCEEDEDjob not found — API Error: Job / operation not found or expired (async task ID unknown) (API)job not foundReceived message larger than max — gRPC Error: 8 RESOURCE_EXHAUSTED: Received message larger than max (x vs. 4194304) (API)Received message larg…12 UNIMPL…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.