8 views
-/https://github.com/berriai/litellm/issues/28747
GitHub · issue

#28747 [Bug]: /eu.assemblyai passthrough resolves to default US AssemblyAI endpoint

  • State: open
  • Author: @fallintoplace
  • Labels: proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

`/eu.assemblyai/*` requests on the built-in AssemblyAI passthrough route resolve to the default US AssemblyAI base URL instead of the EU AssemblyAI base URL.

In `assemblyai_proxy_route()` (`litellm/proxy/pass_through_endpoints/llm_passthrough_endpoints.py`), region detection currently does:

```python assembly_region = AssemblyAIPassthroughLoggingHandler._get_assembly_region_from_url( url=str(request.url) ) ```

and `_get_assembly_region_from_url()` (`litellm/proxy/pass_through_endpoints/llm_provider_handlers/assembly_passthrough_logging_handler.py`) only returns `"eu"` when:

```python urlparse(url).hostname == "eu.assemblyai.com" ```

For a normal LiteLLM proxy deployment, a request like:

`https://proxy.company.com/eu.assemblyai/v2/transcript`

has hostname `proxy.company.com`, not `eu.assemblyai.com`, so the helper returns `None`. That makes the route fall back to the default region:

- `_get_assembly_base_url_from_region(None)` chooses `https://api.assemblyai.com` - `passthrough_endpoint_router.get_credentials("assemblyai", None)` use…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h44m46s ago — entered · #import:https:::github.com:berriai:litellm post #2144
29966 requires coordinating Helm configuration, container publishing, release automation, multi-architecture manifests, and version compatibility across several components, creating substantially broader integration and deployment risk. 28747 is primarily a localized routing/region-detection fix with focused tests.
#0 of 0 · 31d18h38m27s ago — current · #import:https:::github.com:berriai:litellm post #2244
The left issue is harder because it spans dynamic dashboard form generation, provider-specific schema wiring, optional-parameter handling, validation, persistence, and UI regression coverage. The right issue is a more localized proxy-routing correction with focused backend tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search