[GH-ISSUE #16055] issue: updateDirectConnectionsHandler is not defined browser console error when saving settings in admin connections tab #17768

New Issue

GiteaMirror · 2026-04-19T23:39:07-05:00

GiteaMirror commented

2026-04-19 23:39:07 -05:00

Originally created by @silentoplayz on GitHub (Jul 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16055

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.18 (5fbfe2bdca)

Ollama Version (if applicable)

v0.9.5 (5d8c173529)

Operating System

Ubuntu 24.04.2 LTS

Browser (if applicable)

Mozilla Firefox Debian Package (mozilla-deb - 1.0) v141.0 (64-bit)

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 JavaScript errors should be displayed in the browser console when saving settings within the "Connections" tab of the admin panel settings. The settings should save successfully without any client-side errors.

Actual Behavior

Upon clicking the "Save" button in the "Connections" tab of the admin panel settings, an Uncaught (in promise) ReferenceError: updateDirectConnectionsHandler is not defined error is displayed in the browser console. This error occurs even if no changes have been made to the settings. While the error does not prevent the settings from being saved, it indicates an underlying JavaScript issue.

Steps to Reproduce

Ensure you are running Open WebUI version v0.6.18 (commit 5fbfe2bdcadf5f157926f6551891e4dc0802b9f3) or later on the dev branch.
Log in to Open WebUI as an administrator.
Navigate to the "Admin Panel", followed by "Settings" from this menu.
Select the "Connections" tab from the settings menu.
Click the "Save" button at the bottom of the "Connections" tab.
Open up the browser console (usually F12 key on the keyboard) and observe the browser console for the error.

Logs & Screenshots

Browser Console Log:

Uncaught (in promise) ReferenceError: updateDirectConnectionsHandler is not defined
    C Connections.svelte:199
    It dom.js:371
    D dom.js:361
    m Connections.svelte:425
    _t Component.js:44
    m Tools.svelte:55
    p Settings.svelte:411
    ht scheduler.js:119
    dt scheduler.js:79
    promise callback*ft scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    $$set root.svelte:69
    $set Component.js:507
    ee client.js:1576
    Ce client.js:398
    An client.js:1926
    d Settings.svelte:122
    D dom.js:361
    m Settings.svelte:516
    _t Component.js:44
    m Immutable
    _t Component.js:44
    p root.svelte:53
    kt utils.js:203
    p +layout.svelte:78
    p +layout.svelte:27
    ht scheduler.js:119
    dt scheduler.js:79
    promise callback*ft scheduler.js:20
    ht Component.js:81
    ctx Component.js:139
    $$set root.svelte:69
    $set Component.js:507
    ee client.js:1576
    Sn client.js:2368
    setTimeout handler*Sn/</</< client.js:2362
    Sn client.js:2361
    Sn client.js:2360
Connections.svelte:199:3

Docker Container Logs:
(No relevant Docker container logs observed for this client-side error.)

Screenshot:

Additional Information

This error has been consistently reproduced on both a production-like dev instance (Docker installation) and a fresh local development instance (built from dev branch). While the error doesn't seem to prevent settings from being saved, it indicates a client-side JavaScript issue that should be addressed for stability and clean console output.

Originally created by @silentoplayz on GitHub (Jul 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16055 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.18 (https://github.com/open-webui/open-webui/commit/5fbfe2bdcadf5f157926f6551891e4dc0802b9f3) ### Ollama Version (if applicable) v0.9.5 (https://github.com/ollama/ollama/commit/5d8c1735296299c3d81bb40f00038398dc729579) ### Operating System Ubuntu 24.04.2 LTS ### Browser (if applicable) Mozilla Firefox Debian Package (mozilla-deb - 1.0) v141.0 (64-bit) ### 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 JavaScript errors should be displayed in the browser console when saving settings within the "Connections" tab of the admin panel settings. The settings should save successfully without any client-side errors. ### Actual Behavior Upon clicking the "Save" button in the "Connections" tab of the admin panel settings, an `Uncaught (in promise) ReferenceError: updateDirectConnectionsHandler is not defined` error is displayed in the browser console. This error occurs even if no changes have been made to the settings. While the error does not prevent the settings from being saved, it indicates an underlying JavaScript issue. ### Steps to Reproduce 1. Ensure you are running Open WebUI version `v0.6.18` (commit `5fbfe2bdcadf5f157926f6551891e4dc0802b9f3`) or later on the `dev` branch. 2. Log in to Open WebUI as an administrator. 3. Navigate to the "Admin Panel", followed by "Settings" from this menu. 4. Select the "Connections" tab from the settings menu. 5. Click the "Save" button at the bottom of the "Connections" tab. 6. Open up the browser console (usually `F12` key on the keyboard) and observe the browser console for the error. ### Logs & Screenshots **Browser Console Log:** ```js Uncaught (in promise) ReferenceError: updateDirectConnectionsHandler is not defined C Connections.svelte:199 It dom.js:371 D dom.js:361 m Connections.svelte:425 _t Component.js:44 m Tools.svelte:55 p Settings.svelte:411 ht scheduler.js:119 dt scheduler.js:79 promise callback*ft scheduler.js:20 ht Component.js:81 ctx Component.js:139 $$set root.svelte:69 $set Component.js:507 ee client.js:1576 Ce client.js:398 An client.js:1926 d Settings.svelte:122 D dom.js:361 m Settings.svelte:516 _t Component.js:44 m Immutable _t Component.js:44 p root.svelte:53 kt utils.js:203 p +layout.svelte:78 p +layout.svelte:27 ht scheduler.js:119 dt scheduler.js:79 promise callback*ft scheduler.js:20 ht Component.js:81 ctx Component.js:139 $$set root.svelte:69 $set Component.js:507 ee client.js:1576 Sn client.js:2368 setTimeout handler*Sn/</</< client.js:2362 Sn client.js:2361 Sn client.js:2360 Connections.svelte:199:3 ``` **Docker Container Logs:** *(No relevant Docker container logs observed for this client-side error.)* **Screenshot:** <img width="2560" height="1280" alt="Image" src="https://github.com/user-attachments/assets/4ec0557b-7a3b-4973-bc83-0e6002e5e7cd" /> ### Additional Information This error has been consistently reproduced on both a production-like dev instance (Docker installation) and a fresh local development instance (built from `dev` branch). While the error doesn't seem to prevent settings from being saved, it indicates a client-side JavaScript issue that should be addressed for stability and clean console output.

GiteaMirror added the bug label 2026-04-19 23:39:07 -05:00

GiteaMirror closed this issue

2026-04-19 23:39:08 -05:00

GiteaMirror commented

2026-04-19 23:39:10 -05:00

@silentoplayz commented on GitHub (Jul 27, 2025):

I've found the fix for this bug! It's a one-line change in /src/lib/components/admin/Settings/Connections.svelte. On line 199, the function updateDirectConnectionsHandler is called, but it should be updateConnectionsHandler. Correcting this typo resolves the Uncaught (in promise) ReferenceError error.

Just like my helpful comment left here. I don't believe a PR is warranted for this fix, but I do urge the maintainer to solve this issue promptly! I have personally tested the fix and the error is no longer thrown in the browser console and settings are save successfully.

@silentoplayz commented on GitHub (Jul 27, 2025): I've found the fix for this bug! It's a one-line change in [/src/lib/components/admin/Settings/Connections.svelte](https://github.com/open-webui/open-webui/blob/main/src/lib/components/admin/Settings/Connections.svelte#L199). On line 199, the function `updateDirectConnectionsHandler` is called, but it should be `updateConnectionsHandler`. Correcting this typo resolves the `Uncaught (in promise) ReferenceError` error. Just like my helpful comment left [here](https://github.com/open-webui/open-webui/issues/16056#issuecomment-3124156184). I don't believe a PR is warranted for this fix, but I do urge the maintainer to solve this issue promptly! I have personally tested the fix and the error is no longer thrown in the browser console and settings are save successfully.

GiteaMirror commented

2026-04-19 23:39:11 -05:00

@tjbck commented on GitHub (Jul 28, 2025):

Addressed with 807c34b40c

@tjbck commented on GitHub (Jul 28, 2025): Addressed with 807c34b40c2efa7446ca6332b531f329664c973e

GiteaMirror commented

2026-04-19 23:39:11 -05:00

@silentoplayz commented on GitHub (Jul 29, 2025):

Addressed with 807c34b

While this does prevent the error from being thrown in the browser console that I was getting, is it the proper fix? These are the toast notifications that are displayed to me upon saving changes on the Connections page with the removal of the updateDirectConnectionsHandler line:

The Settings saved successfully! toast notification comes from elsewhere; likely from /src/lib/components/admin/Settings.svelte:

And these are the toast notifications that are displayed to me upon saving changes on the Connections page with the rename of updateDirectConnectionsHandler to updateConnectionsHandler:

Here, we observe that the Settings saved successfully! toast notification does not appear, but then we also gain a Connection settings updated toast notification.

The Connection settings updated toast notification is triggered by the following lines of code, but this only gets triggered with a rename of updateDirectConnectionsHandler to updateConnectionsHandler.

	const updateConnectionsHandler = async () => {
		const res = await setConnectionsConfig(localStorage.token, connectionsConfig).catch((error) => {
			toast.error(`${error}`);
		});

		if (res) {
			toast.success($i18n.t('Connections settings updated'));
			await models.set(await getModels());
		}
	};

@silentoplayz commented on GitHub (Jul 29, 2025): > Addressed with [807c34b](https://github.com/open-webui/open-webui/commit/807c34b40c2efa7446ca6332b531f329664c973e) While this does prevent the error from being thrown in the browser console that I was getting, is it the proper fix? These are the toast notifications that are displayed to me upon saving changes on the `Connections` page with the removal of the `updateDirectConnectionsHandler` line: <img width="416" height="259" alt="Image" src="https://github.com/user-attachments/assets/43d822f7-3aea-414a-8b5c-03816ecee431" /> The `Settings saved successfully!` toast notification comes from elsewhere; likely from `/src/lib/components/admin/Settings.svelte`: <img width="461" height="527" alt="Image" src="https://github.com/user-attachments/assets/7a9d19bf-b4a4-4e33-b1c7-fe1ea817ba6e" /> And these are the toast notifications that are displayed to me upon saving changes on the `Connections` page with the rename of `updateDirectConnectionsHandler` to `updateConnectionsHandler`: <img width="416" height="259" alt="Image" src="https://github.com/user-attachments/assets/48815cb7-4505-434c-834d-0546dcd14e64" /> Here, we observe that the `Settings saved successfully!` toast notification does not appear, but then we also gain a `Connection settings updated` toast notification. The `Connection settings updated` toast notification is triggered by the following lines of code, but this only gets triggered with a rename of `updateDirectConnectionsHandler` to `updateConnectionsHandler`. ```js const updateConnectionsHandler = async () => { const res = await setConnectionsConfig(localStorage.token, connectionsConfig).catch((error) => { toast.error(`${error}`); }); if (res) { toast.success($i18n.t('Connections settings updated')); await models.set(await getModels()); } }; ```

GiteaMirror referenced this issue

2026-04-20 00:36:45 -05:00

[GH-ISSUE #17768] issue: MCP feature doesn't support multi-tenant use case #18392

GiteaMirror referenced this issue

2026-04-25 07:48:08 -05:00

[GH-ISSUE #17768] issue: MCP feature doesn't support multi-tenant use case #33921

GiteaMirror referenced this issue

2026-05-05 20:32:00 -05:00

[GH-ISSUE #17768] issue: MCP feature doesn't support multi-tenant use case #57058

Sign in to join this conversation.