BerriAI/litellm · error · GigaChatAuthError
GigaChat authentication failed: {e.response.text}
Error message
GigaChat authentication failed: {e.response.text} What it means
Error "GigaChat authentication failed: {e.response.text}" thrown in BerriAI/litellm.
Source
Thrown at litellm/llms/gigachat/authenticator.py:174
Returns:
Tuple of (access_token, expires_at_ms)
"""
headers: Final = {
"Authorization": f"Basic {credentials}",
"RqUID": str(uuid.uuid4()),
"Content-Type": "application/x-www-form-urlencoded",
}
data: Final = {"scope": scope}
verbose_logger.debug("Requesting GigaChat access token from %s", auth_url)
try:
client: Final = _get_http_client()
response: Final = client.post(auth_url, headers=headers, data=data, timeout=30)
response.raise_for_status()
return _parse_token_response(response)
except httpx.HTTPStatusError as e:
raise GigaChatAuthError(
status_code=e.response.status_code,
message=f"GigaChat authentication failed: {e.response.text}",
)
except httpx.RequestError as e:
raise GigaChatAuthError(
status_code=500,
message=f"GigaChat authentication request failed: {e}",
)
async def _request_token_async(
credentials: str,
scope: str,
auth_url: str,
) -> tuple[str, int]:
"""Async version of _request_token_sync."""
headers: Final = {
"Authorization": f"Basic {credentials}",View on GitHub (pinned to 6c2dcb801b)
Solutions
- Check the GigaChat credentials; see the API error text.
When it happens
Trigger: Thrown at litellm/llms/gigachat/authenticator.py:174 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- Authentication and authorization failures — expired tokens, bad credentials, and missing scopes.
AI-assisted analysis of BerriAI/litellm@6c2dcb801b (2026-08-15).
Data as JSON: /api/errors/4f7e141a19d8b33b.
Report an issue: GitHub.