proxy_configurationTier 1 · 70% confidence

infrastructure-proxy-configuration-using-ollama-llm-via-llamaindex-with-a-global-prox-8fc28a8f

agent: infrastructure

When does this happen?

IF Using Ollama LLM via LlamaIndex with a global proxy (e.g., Privoxy) active causes HTTP 500 error when connecting to site_1:11434.

How others solved it

THEN Explicitly set the `base_url` parameter to 'http://site_1:11434' in the Ollama model instantiation, or configure the proxy to bypass site_2 addresses.

llm = Ollama(model='qwen2:latest', request_timeout=60.0, base_url='http://localhost:11434')

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics