BerriAI/litellm · error · ProxyException

Internal Server Error({e})

Error message

Internal Server Error({e})

What it means

Catch-all of the team logging-disable endpoint: legitimate 4xx exceptions are re-raised untouched, but any remaining exception is logged and wrapped as ProxyException 'Internal Server Error({e})' with 500, giving the caller a uniform error envelope.

Source

Thrown at litellm/proxy/management_endpoints/team_callback_endpoints.py:591

                "team_id": team_id,
                "success_callbacks": team_callback_settings_obj.success_callback,
                "failure_callbacks": team_callback_settings_obj.failure_callback,
                "callback_vars": team_callback_settings_obj.callback_vars,
            },
        }

    except HTTPException:
        # Legitimate 4xx (e.g. 403 from the access guard) — re-raise
        # without the error-level log noise that the catch-all below
        # would produce.
        raise
    except ProxyException:
        raise
    except Exception as e:
        verbose_proxy_logger.error("litellm.proxy.proxy_server.get_team_callbacks(): Exception occurred - %s", e)
        verbose_proxy_logger.debug(traceback.format_exc())
        if isinstance(e, HTTPException):
            raise ProxyException(
                message=getattr(e, "detail", f"Internal Server Error({e})"),
                type=ProxyErrorTypes.internal_server_error.value,
                param=getattr(e, "param", "None"),
                code=getattr(e, "status_code", status.HTTP_500_INTERNAL_SERVER_ERROR),
            )
        elif isinstance(e, ProxyException):
            raise 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,
        )

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check proxy server logs for the underlying exception details.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/team_callback_endpoints.py:591 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/e8847c07db933741. Report an issue: GitHub.