[GH-ISSUE #22228] issue: Unable to listen web events in Artifacts iframe

GiteaMirror commented

2026-04-20 02:11:10 -05:00

Owner

Originally created by @ShirasawaSama on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22228

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

Git Clone

Open WebUI Version

v0.8.8

Ollama Version (if applicable)

No response

Operating System

MacOS

Browser (if applicable)

No response

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

No errors reported

Actual Behavior

When opening the iframe in artifacts, an error will be reported directly.

Steps to Reproduce

Just open the iframe in Artifacts.

Logs & Screenshots

Additional Information

No response

Originally created by @ShirasawaSama on GitHub (Mar 4, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22228 ### 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 Git Clone ### Open WebUI Version v0.8.8 ### Ollama Version (if applicable) _No response_ ### Operating System MacOS ### Browser (if applicable) _No response_ ### 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 No errors reported ### Actual Behavior When opening the iframe in artifacts, an error will be reported directly. ### Steps to Reproduce Just open the iframe in Artifacts. ### Logs & Screenshots <img width="907" height="132" alt="Image" src="https://github.com/user-attachments/assets/fb2bf52e-4827-4fbf-acc9-8abde7680dea" /> ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-20 02:11:10 -05:00

GiteaMirror closed this issue

2026-04-20 02:11:11 -05:00

GiteaMirror commented

2026-04-20 02:11:11 -05:00

Author

Owner

@ShirasawaSama commented on GitHub (Mar 4, 2026):

The reason I got that error is because I did not enable cross origin iframe setting in the user interface settings (near the bottom)

@ShirasawaSama commented on GitHub (Mar 4, 2026): <img width="1004" height="133" alt="Image" src="https://github.com/user-attachments/assets/caa8b801-fd11-4c6b-a194-425fc5516e5b" /> The reason I got that error is because I did not enable cross origin iframe setting in the user interface settings (near the bottom)

GiteaMirror referenced this issue

2026-04-20 05:52:31 -05:00

[PR #19670] [MERGED] fix: Correct web search filter logic to consistently block filtered domains #25303

GiteaMirror referenced this issue

2026-04-25 13:17:41 -05:00

[PR #19670] [MERGED] fix: Correct web search filter logic to consistently block filtered domains #40933

GiteaMirror referenced this issue

2026-04-30 00:03:21 -05:00

[PR #19670] [MERGED] fix: Correct web search filter logic to consistently block filtered domains #48351

GiteaMirror referenced this issue

2026-05-06 09:31:05 -05:00

[PR #19670] [MERGED] fix: Correct web search filter logic to consistently block filtered domains #64159