Cause (Documented platform behavior): Initialization resolves key/baseURL from config or per-user stored values and throws when absent. Fix status: documented_behavior Limitations: - Endpoint-rename cause inferred from lookup-by-name logic. Other error fragments: - Base URL not p
Cause (Documented platform behavior): The server rejects explicit think=true for models lacking CapabilityThinking on the native API; the Anthropic compatibility middleware sets relax_thinking so tools like Claude Code are not rejected. Fix status: documented_behavior Evidence (p
Cause (Documented platform behavior): Documented known limitation: general MPI+Slurm configuration issue, not TRT-LLM specific. Fix status: documented_behavior Limitations: - srun --mpi / mpirun alternatives are general guidance; docs defer to cluster admin. Other error fragments
Cause (Documented platform behavior): After env substitution, a value still matching /^\${(.+)}$/ means the variable was unset. Fix status: documented_behavior Other error fragments: - Missing Base URL for Evidence (public sources, summarized; not reproduced by this contributor):
Cause (Documented platform behavior): Version compare only; not fatal. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/danny-avila/LibreChat/d297530def0228607627ea4c01a6147a71f1c0c1/pac
Cause (Documented platform behavior): openai-node detects a fetch failure whose cause.code is UND_ERR_HEADERS_TIMEOUT and throws APIConnectionTimeoutError with the explanatory message (cause attached); otherwise it throws a plain APIConnectionTimeoutError ('Request timed out.').
Cause (Documented platform behavior): Chromium classifies these as CORS errors of type kLocalNetworkAccessPermissionDenied / kInsecureLocalNetwork / kInvalidLocalNetworkAccess, independent of Access-Control-Allow-* headers. Fix status: documented_behavior Limitations: - Chrome ve
Cause (Documented platform behavior): Security hardening: without a master key the proxy accepts every request unauthenticated, and sk-1234 is publicly known, so boot is refused unless an explicit local-dev override is set. Fix status: documented_behavior Workaround (not a fix):
Cause (Documented platform behavior): Documented gotchas. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/Mozilla-Ocho/llamafile/4a9be84a8d788cbd7784f815e825c641f9bf869a/docs/troublesho
Cause (Documented platform behavior): Chromium reports kMissingAllowOriginHeader whenever the response lacks the header, regardless of status code; the script sees only a network error, so the underlying 4xx/5xx is hidden unless the Network panel is inspected. Fix status: documen
Cause (Documented platform behavior): Documented Windows 4GB executable limit. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/Mozilla-Ocho/llamafile/4a9be84a8d788cbd7784f815e825c641f9b
Cause (Documented platform behavior): Config is validated with a strict zod schema; special hints for imageOutputType and speech config. Fix status: documented_behavior Other error fragments: - The Speech-to-text and Text-to-speech configuration format has recently changed. Evide
Cause (Documented platform behavior): Virtual keys, teams and stored credentials are persisted in the proxy database; repositories raise when prisma_client is None. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https:
Cause (Documented platform behavior): Loader returns null when the local file is absent or YAML load fails and continues with defaults (logged at info level, easy to miss). Fix status: documented_behavior Limitations: - Docker mount advice is general deployment knowledge;
Cause (Documented platform behavior): Ollama router guards on the setting. Fix status: documented_behavior Limitations: - Persistent-config override note not verified in fetched sources. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.gith
Cause (Documented platform behavior): aiohttp documents that, contrary to requests, it does not read proxy environment variables by default; passing trust_env=True makes it use urllib.request.getproxies() (HTTP_PROXY etc., NO_PROXY honored). Fix status: documented_behavior Limita
Cause (Documented platform behavior): Single-user no-auth mode only allowed on fresh installs. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/open-webui/open-webui/8bd8b4fac5e059578ac0
Cause (Documented platform behavior): For credentialed requests Chromium requires an explicit echoing origin and Access-Control-Allow-Credentials: true; wildcard origin is rejected (kWildcardOriginNotAllowed), and a non-'true' Allow-Credentials value is rejected (kInvalidAllowCre
Cause (Documented platform behavior): Documented gotcha: binfmt_misc registrations. Fix status: documented_behavior Limitations: - Exact user-visible error text varies by distro; only "run-detectors" is quoted by docs. Evidence (public sources, summarized; not reproduced by this
Cause (Documented platform behavior): After header parsing, an empty api_key string means the Bearer prefix was missing; a None key means no key header was supplied. Fix status: documented_behavior Limitations: - HTTP status mapping to 401 is general proxy behaviour,