[GH-ISSUE #21922] issue: Images fail to load behind reverse proxy in 0.8.x (LAN works, internet broken)

Originally created by @Hellrabb on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21922 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.8.3 ### Ollama Version (if applicable) _No response_ ### Operating System ubuntu 24.04 ### Browser (if applicable) chrome 143 ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Whether accessed via LAN IP or public domain name (WAF/reverse proxy), the following elements from the same instance should display correctly: - Images within RAG results - Images returned by web searches Additionally, image URLs should be externally accessible addresses, not links restricted to internal networks. ### Actual Behavior Local network access (e.g., <http://192.168.x.x:3000>):All images display normally.(Images are displayed via URLs included in the tool's return results) Public domain address access (e.g., <https://openwebui.example.com>): Image locations appear blank or display loading failure icons; In the browser's Network panel, image request URLs point to internal network addresses (e.g., <http://192.168.x.x/...>) or other invalid links; Since these links are inaccessible from the external network, images fail to display. ### Steps to Reproduce 1. Deploy Open WebUI 0.8.x on a LAN server (e.g., Docker, listening at <http://192.168.x.x:3000>). 2. Access via the LAN address in your browser, e.g., <http://192.168.x.x:3000>. 3. In the chat: Trigger a RAG search and receive results with images. Verify images display correctly when accessed via the LAN. 4. Configure a WAF/reverse proxy to expose an external domain, e.g., <https://openwebui.example.com>, pointing to the same Open WebUI instance. 5. Access <https://openwebui.example.com> from an external browser, log into the same instance, and perform the same operations as in step 3. Observation: Images fail to display. The browser developer tools (Network tab) show image requests pointing to internal network addresses or invalid paths, causing loading failures. ### Logs & Screenshots The image element in the Chrome console is: <img draggable="false" data-cy="image" src="http://xx.xx.xx.xx:aabb/..." alt="检索到的图片" class="rounded-lg"> ### Additional Information I've already tried newer versions (such as 0.8.5), and the situation appears different—image links revert to a default path. Due to environmental constraints, I'll conduct further testing and add screenshots if needed.

GiteaMirror commented

2026-04-25 09:22:29 -05:00

Owner

Originally created by @Hellrabb on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21922

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.8.3

Ollama Version (if applicable)

No response

Operating System

ubuntu 24.04

Browser (if applicable)

chrome 143

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Whether accessed via LAN IP or public domain name (WAF/reverse proxy), the following elements from the same instance should display correctly:

Images within RAG results
Images returned by web searches

Additionally, image URLs should be externally accessible addresses, not links restricted to internal networks.

Actual Behavior

Local network access (e.g., http://192.168.x.x:3000):All images display normally.(Images are displayed via URLs included in the tool's return results)
Public domain address access (e.g., https://openwebui.example.com):
Image locations appear blank or display loading failure icons;
In the browser's Network panel, image request URLs point to internal network addresses (e.g., http://192.168.x.x/...) or other invalid links;
Since these links are inaccessible from the external network, images fail to display.

Steps to Reproduce

Deploy Open WebUI 0.8.x on a LAN server (e.g., Docker, listening at http://192.168.x.x:3000).
Access via the LAN address in your browser, e.g., http://192.168.x.x:3000. 3. In the chat:
Trigger a RAG search and receive results with images.
Verify images display correctly when accessed via the LAN.
Configure a WAF/reverse proxy to expose an external domain, e.g., https://openwebui.example.com, pointing to the same Open WebUI instance.
Access https://openwebui.example.com from an external browser, log into the same instance, and perform the same operations as in step 3.
Observation: Images fail to display. The browser developer tools (Network tab) show image requests pointing to internal network addresses or invalid paths, causing loading failures.

Logs & Screenshots

The image element in the Chrome console is:

Additional Information

I've already tried newer versions (such as 0.8.5), and the situation appears different—image links revert to a default path. Due to environmental constraints, I'll conduct further testing and add screenshots if needed.

GiteaMirror added the bug label 2026-04-25 09:22:29 -05:00

GiteaMirror closed this issue

2026-04-25 09:22:30 -05:00

[GH-ISSUE #21922] issue: Images fail to load behind reverse proxy in 0.8.x (LAN works, internet broken) #35146