Web Search use Google PSE causes core dump #1464

New Issue

2025-11-11T14:45:47-06:00

GiteaMirror commented

2025-11-11 14:45:47 -06:00

Originally created by @luochen1990 on GitHub (Jul 8, 2024).

Bug Report

Description

Bug Summary:

I'm using Open WebUI via NixOS, I configured Google PSE and tries to search something, but It core dumped after some seconds, from the journalctl output it seems the search result is received, but something went wrong when processing the search result. (Not sure I provided the correct Google PSE Engine ID, but I can not find a more possible correct one)

Unexpected token '<', "<html>
<h"... is not valid JSON

Steps to Reproduce:

Enable web search on Open-WebUI, and select Google PSE
Fill in Goolge PSE API Key which looks like AIzaSyDT7xxxxxxxxxxxxxxxxxxxxxXwuLj-oaw and engine ID which looks like b73dxxxxxxxx943b4
Start a new conversation and enable "Web Search"
Ask a question like "what's the different between nixpkgs.config.cudaSupport and hardware.graphics.enable in NixOS?"
Confirm that the service is core dumped from journalctl -u open-webui

Expected Behavior:

No error happen and the search results is returned successfully.

Actual Behavior:

Web page error alert:

Unexpected token '<', "<html>
<h"... is not valid JSON

Environment

Open WebUI Version: [e.g., 0.1.120]
v0.3.7
Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]
Not used
Operating System:

$ neofetch --stdout
OS: NixOS 24.11.20240701.00d80d1 (Vicuna) x86_64
Host: Techvision TVI7309X
Kernel: 6.6.32
Uptime: 20 days, 3 hours, 20 mins
Packages: 1945 (nix-system), 243 (nix-user)
Shell: zsh 5.9
Resolution: 3440x1440
WM: KWin
Icons: Papirus-Dark [GTK2/3]
Terminal: /dev/pts/1
CPU: Intel Celeron N5105 (4) @ 2.900GHz
GPU: Intel JasperLake [UHD Graphics]
Memory: 5619MiB / 15843MiB

Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Microsoft Edge
Version 126.0.2592.68 (Official build) (64-bit)

Reproduction Details

Confirmation:

I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:

Browser console error:

Unchecked runtime.lastError: Specified native messaging host not found.

Docker Container Logs:

journalctl -u open-webui:

systemd[1]: open-webui.service: Main process exited, code=dumped, status=8/FPE
systemd[1]: open-webui.service: Failed with result 'core-dump'.

Screenshots (if applicable):

https://discord.com/channels/1170866489302188073/1258256860453277830

Installation Method

Installed via NixOS:

    services.open-webui = {
      enable = true;
      host = "0.0.0.0";
      port = 5090;
    };

The packaging nix expression is: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/op/open-webui/package.nix

The systemd unit is defined via: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/misc/open-webui.nix#L84

Originally created by @luochen1990 on GitHub (Jul 8, 2024). # Bug Report ## Description **Bug Summary:** I'm using Open WebUI via NixOS, I configured Google PSE and tries to search something, but It core dumped after some seconds, from the journalctl output it seems the search result is received, but something went wrong when processing the search result. (Not sure I provided the correct Google PSE Engine ID, but I can not find a more possible correct one) ``` Unexpected token '<', "<html> <h"... is not valid JSON ``` **Steps to Reproduce:** 1. Enable web search on Open-WebUI, and select Google PSE 2. Fill in Goolge PSE API Key which looks like `AIzaSyDT7xxxxxxxxxxxxxxxxxxxxxXwuLj-oaw ` and engine ID which looks like `b73dxxxxxxxx943b4` 3. Start a new conversation and enable "Web Search" 4. Ask a question like "what's the different between nixpkgs.config.cudaSupport and hardware.graphics.enable in NixOS?" 5. Confirm that the service is core dumped from `journalctl -u open-webui` **Expected Behavior:** No error happen and the search results is returned successfully. **Actual Behavior:** Web page error alert: ``` Unexpected token '<', "<html> <h"... is not valid JSON ``` ## Environment - **Open WebUI Version:** [e.g., 0.1.120] v0.3.7 - **Ollama (if applicable):** [e.g., 0.1.30, 0.1.32-rc1] Not used - **Operating System:** ``` $ neofetch --stdout OS: NixOS 24.11.20240701.00d80d1 (Vicuna) x86_64 Host: Techvision TVI7309X Kernel: 6.6.32 Uptime: 20 days, 3 hours, 20 mins Packages: 1945 (nix-system), 243 (nix-user) Shell: zsh 5.9 Resolution: 3440x1440 WM: KWin Icons: Papirus-Dark [GTK2/3] Terminal: /dev/pts/1 CPU: Intel Celeron N5105 (4) @ 2.900GHz GPU: Intel JasperLake [UHD Graphics] Memory: 5619MiB / 15843MiB ``` - **Browser (if applicable):** [e.g., Chrome 100.0, Firefox 98.0] Microsoft Edge Version 126.0.2592.68 (Official build) (64-bit) ## Reproduction Details **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on 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. ## Logs and Screenshots **Browser Console Logs:** Browser console error: ``` Unchecked runtime.lastError: Specified native messaging host not found. ``` **Docker Container Logs:** journalctl -u open-webui: ``` systemd[1]: open-webui.service: Main process exited, code=dumped, status=8/FPE systemd[1]: open-webui.service: Failed with result 'core-dump'. ``` **Screenshots (if applicable):** https://discord.com/channels/1170866489302188073/1258256860453277830 ## Installation Method Installed via NixOS: ```nix services.open-webui = { enable = true; host = "0.0.0.0"; port = 5090; }; ``` The packaging nix expression is: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/op/open-webui/package.nix The systemd unit is defined via: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/nixos/modules/services/misc/open-webui.nix#L84

GiteaMirror closed this issue

2025-11-11 14:45:47 -06:00

GiteaMirror referenced this issue

2025-11-11 17:27:33 -06:00

[PR #1464] [MERGED] Allow using external ollama service. #7474

GiteaMirror referenced this issue

2026-04-20 03:07:00 -05:00

[PR #1464] [MERGED] Allow using external ollama service. #20678

GiteaMirror referenced this issue

2026-04-25 10:14:55 -05:00

[PR #1464] [MERGED] Allow using external ollama service. #36308

GiteaMirror referenced this issue