21 views
-/https://github.com/berriai/litellm/issues/22965
GitHub · issue

#22965 [Bug]: VertexAI - unable to use 3rd party model - Qwen 3.5 with dedicated endpoint

  • State: open
  • Author: @wojciehm
  • Labels: bug, proxy, llm translation

### Check for existing issues

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

### What happened?

Hi.

I am following version of LiteLLM as Docker.

```Name: litellm Version: 1.81.14 Summary: Library to easily interface with LLM API providers Home-page: https://litellm.ai Author: BerriAI Author-email: License: MIT Location: /usr/lib/python3.13/site-packages Requires: aiohttp, click, fastuuid, httpx, importlib-metadata, jinja2, jsonschema, openai, pydantic, python-dotenv, tiktoken, tokenizers Required-by: semantic-router ``` I have some local ollama models which are working together with Open WebUI and one endpoint is VertexAI.

Docker Compose ``` services: db: image: postgres:16 container_name: llm-db restart: always environment: POSTGRES_DB: ${POSTGRES_DB} POSTGRES_USER: ${POSTGRES_USER} POSTGRES_PASSWORD: ${POSTGRES_PASSWORD} volumes: - /mnt/AppData/llm-stack/postgres:/var/lib/postgresql/data - /etc/localtime:/etc/localtime:ro ports: - "${DB_PORT}:5432" networks: - frontend logging: driver: loki options: loki-url: "http://127.0.0.1:3100/loki/a…

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h21m59s ago — entered · #import:https:::github.com:berriai:litellm post #2687
The left issue is harder because it likely spans Vertex-specific endpoint routing, model translation, authentication, and compatibility testing across deployment modes. The right issue is more contained: tracing one identity value through an existing MCP lifecycle with focused regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search