diegosouzapw/OmniRoute · error
TLS_CLIENT_UNAVAILABLE
TLS_CLIENT_UNAVAILABLE
Error message
Grok TLS client unavailable: ${err.message} What it means
Error "Grok TLS client unavailable: ${err.message}" thrown in diegosouzapw/OmniRoute.
Source
Thrown at open-sse/executors/grok-web.ts:963
try {
tlsResult = await tlsFetchGrok(GROK_CHAT_API, {
method: "POST",
headers,
body: JSON.stringify(grokPayload),
timeoutMs: FETCH_TIMEOUT_MS,
signal: combinedSignal,
stream: true,
streamEofSymbol: "[DONE]",
});
} catch (err) {
if (err instanceof TlsClientUnavailableError) {
log?.error?.("GROK-WEB", `TLS client unavailable: ${err.message}`);
const errResp = new Response(
JSON.stringify({
error: {
message: sanitizeErrorMessage(`Grok TLS client unavailable: ${err.message}`),
type: "upstream_error",
code: "TLS_CLIENT_UNAVAILABLE",
},
}),
{ status: 502, headers: { "Content-Type": "application/json" } }
);
return { response: errResp, url: GROK_CHAT_API, headers, transformedBody: grokPayload };
}
log?.error?.("GROK-WEB", `Fetch failed: ${err instanceof Error ? err.message : String(err)}`);
const errResp = new Response(
JSON.stringify({
error: {
message: sanitizeErrorMessage(
`Grok connection failed: ${err instanceof Error ? err.message : String(err)}`
),
type: "upstream_error",
},
}),
{ status: 502, headers: { "Content-Type": "application/json" } }
);View on GitHub (pinned to a179ffed5b)
When it happens
Trigger: Thrown at open-sse/executors/grok-web.ts:963 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- SSL/TLS and certificate errors — how TLS handshakes and certificate validation fail.
AI-assisted analysis of diegosouzapw/OmniRoute@a179ffed5b (2026-08-25).
Data as JSON: /api/errors/998d79e9b32e520c.
Report an issue: GitHub.