mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #24153] issue: v0.9.2 -> can't get model list with no_proxy in an company proxy environment #58878
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @somera on GitHub (Apr 26, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24153
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.9.2
Ollama Version (if applicable)
0.21.2
Operating System
Ubuntu 24.04.4
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
I updated from 0.8.12 to 0.9.2 and my instance can't get any modell list:
I have two (vllm, ollama) http endpoints for models. And my model list is empty.
I run my setup in docker in an company environment with an proxy. no_proxy and NO_PROXY is set.
With 0.8.12 all works fine.
Actual Behavior
Model list is empty.
Steps to Reproduce
I had same problems aftrer upgrade to 0.9.1.
Logs & Screenshots
See above.
Additional Information
No response
@somera commented on GitHub (Apr 26, 2026):
I have the http|https|no_proxy configuration which works fine in 0.8.12 (https://docs.openwebui.com/reference/env-configuration#proxy-settings). But I see in the stacktrackes that the company proxy is blocking. which is wrong.
Why?
Cause we need this entvironment I go back to by 0.8.12 backup.
@rgaricano commented on GitHub (Apr 26, 2026):
you have a timeout error, likely because v0.9.1 introduced stricter timeout controls that don't account for proxy-induced delays.
You can try setting (or increasing) the
AIOHTTP_CLIENT_TIMEOUT_MODEL_LISTenv var (e.g. 60, or disable timeout entirelyAIOHTTP_CLIENT_TIMEOUT_MODEL_LIST="")@somera commented on GitHub (Apr 26, 2026):
The time to get the model list for both endpoints is <1 second. I added now 10s timeout:
Same problem.
Why I see the company proxy in the stack trace?
@somera commented on GitHub (Apr 26, 2026):
With the 10 seconds timeout:
But
on the same VM where Open WebUI is running.
@rgaricano commented on GitHub (Apr 26, 2026):
could do you try with
AIOHTTP_CLIENT_SESSION_SSL: false@somera commented on GitHub (Apr 26, 2026):
With:
I don't see the stack traces now. Only errors:
@somera commented on GitHub (Apr 26, 2026):
Now I'm back to my v0.8.12 backup.
@somera commented on GitHub (Apr 27, 2026):
Can someone confirm a bug in Open WebUI?
@somera commented on GitHub (Apr 28, 2026):
I could upgrate other instance to v0.9.2. And it works.
I don't understand why here
is the proxy set. Cause the ip
10.53.209.12is set inno_proxy. And the same setup works with v0.8.12 fine.@Classic298 commented on GitHub (May 2, 2026):
It is a real Open WebUI regression.
Cause: backend/open_webui/routers/openai.py:574 (and similar) uses aiohttp.ClientSession(trust_env=True) and relies entirely on aiohttp to honor NO_PROXY. The aiohttp==3.13.5 pin in backend/requirements.txt:16 has buggy NO_PROXY matching — 0.8.12 shipped an older aiohttp where it worked. Stack trace confirms: connection still carries proxy=URL('http://proxy.company.de:3128/') despite the IP being in no_proxy.
Fix: bypass the proxy explicitly in code, or change the aiohttp pin.
@somera commented on GitHub (May 3, 2026):
My upgrade works now. I added
to my docker-compose.yaml.