BerriAI/litellm · error · HTTPException
Database not connected. Cannot create access group.
Error message
Database not connected. Cannot create access group.
What it means
Infrastructure guard on access-group creation: prisma_client is None because the proxy runs without a database, but access groups are stored exclusively in the DB. Request rejected with 500 before any write.
Source
Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:406
use_model_ids: Final = has_model_ids
# Validate model_names exist in router (only if using model_names path)
if not use_model_ids and has_model_names:
assert data.model_names is not None
all_valid, missing_models = validate_models_exist(
model_names=data.model_names,
llm_router=llm_router,
)
if not all_valid:
raise HTTPException(
status_code=400,
detail={"error": f"Model(s) not found: {', '.join(missing_models)}"},
)
# Check if database is connected
if prisma_client is None:
raise HTTPException(
status_code=500,
detail={"error": "Database not connected. Cannot create access group."},
)
try:
# Check if access group already exists
existing_access_groups: Final = await get_all_access_groups_from_db(prisma_client=prisma_client)
if data.access_group in existing_access_groups:
raise HTTPException(
status_code=409,
detail={
"error": f"Access group '{data.access_group}' already exists. Use PUT /access_group/{data.access_group}/update to modify it."
},
)
# Update deployments using the appropriate method
if use_model_ids:View on GitHub (pinned to 77b7c6c40c)
Solutions
- Set DATABASE_URL to a PostgreSQL connection string and restart the proxy.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:406 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/2ed2be3b123c9515.
Report an issue: GitHub.