Guides
Error Reference
Common errors, root causes, and concrete fixes.
Error Reference
token verification failed: invalid signature
Cause:
- token signed with wrong key/secret
- stale/revoked key
- project/key mismatch
Fix:
- Mint token from correct project/key.
- Verify key is active (not revoked/rotated away).
- Ensure data plane has up-to-date key status integration.
unknown project id '...'
Cause:
- wrong
project_idsent in handshake - project not created in control plane
Fix:
- Use token-derived project id when possible.
- Ensure project exists and was copied correctly.
decode failed: invalid type: newtype struct, expected a string
Cause:
- malformed payload type field
- payload shape mismatch for room/plugin call
Fix:
- For
room.message, sendp: { type: string, data: any }. - Confirm client codec and server codec negotiation are consistent.
Unknown RPC rid: missing (SDK)
Cause:
- response missing
rid - non-RPC message accidentally routed into RPC resolver path
Fix:
- Ensure only
rpc.responsewith validridenters RPC resolver. - Validate server response construction for every RPC path.
WebSocket handshake errors (No "Connection: upgrade" header, Handshake not finished)
Cause:
- HTTP request sent to WS endpoint
- reverse proxy misconfigured for websocket upgrade
- client connection race/abort
Fix:
- Ensure client uses
ws:///wss://. - Configure proxy upgrade headers correctly.
- Check load balancer websocket support.
CORS errors on control API
Cause:
- missing
Access-Control-Allow-Originfor dashboard/web app origin
Fix:
- Configure allowed origins in control API CORS settings.
- Confirm browser is calling control API URL you expect.
Typed Error Codes
.(('rpc.unknown_rid'));