BerriAI/litellm · error · ProxyException
Internal Server Error, " + str(e)
Error message
Internal Server Error, " + str(e)
What it means
Catch-all of the add-team-callbacks endpoint: HTTPException and ProxyException pass through, but any other exception is logged and re-raised as a ProxyException 'Internal Server Error, ' + str(e) with a 500 status, masking the raw failure into a standard proxy error shape.
Source
Thrown at litellm/proxy/management_endpoints/team_callback_endpoints.py:358
team_id=team_id,
before_metadata=before_metadata,
after_metadata=team_metadata,
user_api_key_dict=user_api_key_dict,
litellm_changed_by=litellm_changed_by,
)
return {
"status": "success",
"data": new_team_row,
}
except HTTPException as e:
raise e
except ProxyException as e:
raise e
except Exception as e:
verbose_proxy_logger.exception("litellm.proxy.proxy_server.add_team_callbacks(): Exception occured - %s", e)
raise ProxyException(
message="Internal Server Error, " + str(e),
type=ProxyErrorTypes.internal_server_error.value,
param=getattr(e, "param", "None"),
code=status.HTTP_500_INTERNAL_SERVER_ERROR,
)
@router.post(
"/team/{team_id}/disable_logging",
tags=["team management"],
dependencies=[Depends(user_api_key_auth)],
)
@management_endpoint_wrapper
async def disable_team_logging(
http_request: Request,
team_id: str,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
litellm_changed_by: str | None = Header(View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy server logs for the underlying exception details.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/team_callback_endpoints.py:358 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- HTTP status errors: handling 4xx and 5xx responses — how to handle 4xx and 5xx responses properly.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/ea34ed16dcbb95a1.
Report an issue: GitHub.