[GH-ISSUE #22753] issue: 404 Error When Sending or Replying to Messages in Any Channel Type #19811

New Issue

GiteaMirror · 2026-04-20T02:18:45-05:00

GiteaMirror commented

2026-04-20 02:18:45 -05:00

Originally created by @silentoplayz on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22753

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

v0.8.10

Ollama Version (if applicable)

v0.18.0

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (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

Sending a message or replying to a message in any channel (Public, Private, Group, or DM) should complete without any console errors. No extraneous API calls should be made for endpoints that do not exist.

Actual Behavior

Every time a message is sent or replies to a message are rendered in any channel type, the frontend immediately fires a GET request to:

/api/v1/channels/{channel_id}/messages/{message_id}/data

The backend responds with 404 Not Found, followed by an unhandled promise rejection in Message.svelte.

Steps to Reproduce

Start an Open WebUI instance utilizing the v0.8.10 version on Ubuntu 24.04.4 LTS using Firefox v148.0.2.
Log in with any user account.
Navigate to any channel (Public Channel, Private Channel, Group Channel, or Direct Message).
Open the browser developer console (F12 → Console tab).
Type any message in the message input and press Enter or click Send.
Observe the browser console immediately after the message renders.

Result: A 404 Not Found error appears for GET /api/v1/channels/{channel_id}/messages/{message_id}/data, followed by:

Uncaught (in promise) We could not find what you're looking for :/ Message.svelte:79

This also reproduces when replying to an existing channel message.

Logs & Screenshots

Browser Console Error (Network)

XHRGET
http://localhost:1337/api/v1/channels/82da4560-335e-45d0-80e5-c15188e7c67b/messages/0ec94e6d-08d6-4d80-8863-48ed1150b531/data
[HTTP/1.1 404 Not Found 96ms]
...
Response headers:
  content-length: 57
  content-type: application/json
  server: uvicorn

Browser Console Exception (JavaScript)

Uncaught (in promise) We could not find what you're looking for :/ Message.svelte:79:10
    Xt Message.svelte:79
    AsyncFunctionThrow self-hosted:784
    (Async: async)
    _i utils.js:41
    map self-hosted:163
    a lifecycle.js:51
    Ce runtime.js:749
    x lifecycle.js:51
    Nr runtime.js:258
    Ye runtime.js:460
    Sn batch.js:762
    Gt batch.js:289
    flush batch.js:417
    ensure batch.js:579
    Fn utils.js:47
    Gn task.js:10
    Se task.js:28
    (Async: VoidFunction)
    Se task.js:19
    ensure batch.js:573
    ct sources.js:193
    le sources.js:171
    E Channel.svelte:200
    mt MessageInput.svelte:547
    keydown MessageInput.svelte:929
    li index-client.js:178
    keydown RichTextInput.svelte:1071
    fl index.js:3122
    someProp index.js:5594
    fl index.js:3120
    e index.js:3089
    (Async: EventListener.handleEvent)
    vg index.js:3088
    Vd index.js:5393
    createView index.js:4981
    mount index.js:4701
    vb index.js:4689
    Wx RichTextInput.svelte:719
    _i utils.js:41
    map self-hosted:163
    a lifecycle.js:51
    Ce runtime.js:749
    x lifecycle.js:51
    Nr runtime.js:258
    Ye runtime.js:460
    Sn batch.js:762
    Gt batch.js:289
    Gt batch.js:314
    flush batch.js:417

Additional Information

The root cause appears to be in src/lib/components/channel/Messages/Message.svelte. The loadMessageData() function is called in onMount whenever message?.data is truthy, calling getMessageData() from src/lib/apis/channels/index.ts:

const loadMessageData = async () => {
    if (message && message?.data) {
        const res = await getMessageData(localStorage.token, channel?.id, message.id);
        if (res) {
            message.data = res;
        }
    }
};

This hits GET /channels/{channel_id}/messages/{message_id}/data, which does not appear to be a registered route on the backend. Since every channel message appears to have a data field (even if empty), this 404 fires on every single message render.

The bug is reproducible on the dev branch with a standard local development setup. It affects all channel types (Public, Private, Group, DM) without exception.

Originally created by @silentoplayz on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22753 ### 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 v0.8.10 ### Ollama Version (if applicable) v0.18.0 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (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 Sending a message or replying to a message in any channel (Public, Private, Group, or DM) should complete without any console errors. No extraneous API calls should be made for endpoints that do not exist. ### Actual Behavior Every time a message is sent or replies to a message are rendered in any channel type, the frontend immediately fires a `GET` request to: ``` /api/v1/channels/{channel_id}/messages/{message_id}/data ``` The backend responds with `404 Not Found`, followed by an unhandled promise rejection in `Message.svelte`. ### Steps to Reproduce ## Steps to Reproduce 1. Start an Open WebUI instance utilizing the `v0.8.10` version on Ubuntu 24.04.4 LTS using Firefox v148.0.2. 3. Log in with any user account. 4. Navigate to any channel (Public Channel, Private Channel, Group Channel, or Direct Message). 5. Open the browser developer console (F12 → Console tab). 6. Type any message in the message input and press Enter or click Send. 7. Observe the browser console immediately after the message renders. **Result**: A `404 Not Found` error appears for `GET /api/v1/channels/{channel_id}/messages/{message_id}/data`, followed by: ``` Uncaught (in promise) We could not find what you're looking for :/ Message.svelte:79 ``` This also reproduces when replying to an existing channel message. ### Logs & Screenshots ### Browser Console Error (Network) ``` XHRGET http://localhost:1337/api/v1/channels/82da4560-335e-45d0-80e5-c15188e7c67b/messages/0ec94e6d-08d6-4d80-8863-48ed1150b531/data [HTTP/1.1 404 Not Found 96ms] ... Response headers: content-length: 57 content-type: application/json server: uvicorn ``` ### Browser Console Exception (JavaScript) ```js Uncaught (in promise) We could not find what you're looking for :/ Message.svelte:79:10 Xt Message.svelte:79 AsyncFunctionThrow self-hosted:784 (Async: async) _i utils.js:41 map self-hosted:163 a lifecycle.js:51 Ce runtime.js:749 x lifecycle.js:51 Nr runtime.js:258 Ye runtime.js:460 Sn batch.js:762 Gt batch.js:289 flush batch.js:417 ensure batch.js:579 Fn utils.js:47 Gn task.js:10 Se task.js:28 (Async: VoidFunction) Se task.js:19 ensure batch.js:573 ct sources.js:193 le sources.js:171 E Channel.svelte:200 mt MessageInput.svelte:547 keydown MessageInput.svelte:929 li index-client.js:178 keydown RichTextInput.svelte:1071 fl index.js:3122 someProp index.js:5594 fl index.js:3120 e index.js:3089 (Async: EventListener.handleEvent) vg index.js:3088 Vd index.js:5393 createView index.js:4981 mount index.js:4701 vb index.js:4689 Wx RichTextInput.svelte:719 _i utils.js:41 map self-hosted:163 a lifecycle.js:51 Ce runtime.js:749 x lifecycle.js:51 Nr runtime.js:258 Ye runtime.js:460 Sn batch.js:762 Gt batch.js:289 Gt batch.js:314 flush batch.js:417 ``` ### Additional Information The root cause appears to be in `src/lib/components/channel/Messages/Message.svelte`. The `loadMessageData()` function is called in `onMount` whenever `message?.data` is truthy, calling `getMessageData()` from `src/lib/apis/channels/index.ts`: ```js const loadMessageData = async () => { if (message && message?.data) { const res = await getMessageData(localStorage.token, channel?.id, message.id); if (res) { message.data = res; } } }; ``` This hits `GET /channels/{channel_id}/messages/{message_id}/data`, which does not appear to be a registered route on the backend. Since every channel message appears to have a `data` field (even if empty), this 404 fires on every single message render. The bug is reproducible on the `dev` branch with a standard local development setup. It affects all channel types (Public, Private, Group, DM) without exception.

GiteaMirror added the confirmed issue bug labels 2026-04-20 02:18:45 -05:00

GiteaMirror closed this issue

2026-04-20 02:18:46 -05:00

GiteaMirror referenced this issue

2026-04-20 05:53:58 -05:00

[PR #19811] [CLOSED] fix: Add proactive OAuth token refresh for MCP sessions #25351

GiteaMirror referenced this issue

2026-04-25 08:33:57 -05:00

[GH-ISSUE #19809] MCP OAuth tokens not proactively refreshed, causing session loss after 1 hour #34533

GiteaMirror referenced this issue

2026-04-25 08:46:01 -05:00

[GH-ISSUE #20291] issue: MCP Atlassian OAuth token refresh fails with "Constructor parameter should be str" in v0.6.43 #34673