[GH-ISSUE #24553] issue: /api/chat/completions runs into error #74932

New Issue

@xcjs commented on GitHub (May 10, 2026):

whipping up a quick fix...

It should be a basically single line change if anyone wants to patch their file locally so they can use 0.9.5.

I use Docker - the best way to resolve that would be to cut a new release.

@xcjs commented on GitHub (May 10, 2026): > whipping up a quick fix... > > It should be a basically single line change if anyone wants to patch their file locally so they can use 0.9.5. I use Docker - the best way to resolve that would be to cut a new release.

GiteaMirror commented

https://github.com/open-webui/open-webui/pull/24556

@Classic298 commented on GitHub (May 10, 2026):

if anyone wants to fix it for their 0.9.5 installation: its a single line fix:

@Classic298 commented on GitHub (May 10, 2026): if anyone wants to fix it for their 0.9.5 installation: its a single line fix: https://github.com/open-webui/open-webui/pull/24556

GiteaMirror commented

@Classic298 commented on GitHub (May 10, 2026):

@xcjs you can easily modify the file within docker

@Classic298 commented on GitHub (May 10, 2026): @xcjs you can easily modify the file within docker

GiteaMirror commented

2026-05-13 07:48:05 -05:00

@Classic298 commented on GitHub (May 10, 2026):

but yeah tim will merge this in for sure

@Classic298 commented on GitHub (May 10, 2026): but yeah tim will merge this in for sure

GiteaMirror commented

@xcjs commented on GitHub (May 10, 2026):

@xcjs you can easily modify the file within docker

I'm aware, but not in my environment. I have orchestration around container deployments, and doing manual patches like that doesn't scale.

An extended Dockerfile is an option, but I'd have to break away from the Github registry/update process we use.

TL;DR: I'll just wait for v.0.9.6/etc. as long as it's coming. :-)

@xcjs commented on GitHub (May 10, 2026): > [@xcjs](https://github.com/xcjs) you can easily modify the file within docker I'm aware, but not in my environment. I have orchestration around container deployments, and doing manual patches like that doesn't scale. An extended Dockerfile is an option, but I'd have to break away from the Github registry/update process we use. TL;DR: I'll just wait for v.0.9.6/etc. as long as it's coming. :-)

GiteaMirror commented

2026-05-13 07:48:05 -05:00

@Classic298 commented on GitHub (May 10, 2026):

For public facing deployments or deployments with higher security requirements I would personally recommend patching that one line, since 0.9.5 has more than a dozen security fixes for vulnerabilities. A dockerfile to patch that one line should be trivial - but yes you do you

Tim will merge it in 100% in 0.9.6. Just not within the hour. May take a day or so

@Classic298 commented on GitHub (May 10, 2026): For public facing deployments or deployments with higher security requirements I would personally recommend patching that one line, since 0.9.5 has more than a dozen security fixes for vulnerabilities. A dockerfile to patch that one line should be trivial - but yes you do you Tim will merge it in 100% in 0.9.6. Just not within the hour. May take a day or so

GiteaMirror commented

2026-05-13 07:48:05 -05:00

@tweinberger-lei commented on GitHub (May 10, 2026):

if anyone wants to fix it for their 0.9.5 installation: its a single line fix:

#24556

confirmed to fix it - thanks!

@tweinberger-lei commented on GitHub (May 10, 2026): > if anyone wants to fix it for their 0.9.5 installation: its a single line fix: > > [#24556](https://github.com/open-webui/open-webui/pull/24556) confirmed to fix it - thanks!

GiteaMirror commented

@somera commented on GitHub (May 11, 2026):

if anyone wants to fix it for their 0.9.5 installation: its a single line fix:

#24556

Works for me. Thx.

@somera commented on GitHub (May 11, 2026): > if anyone wants to fix it for their 0.9.5 installation: its a single line fix: > > [#24556](https://github.com/open-webui/open-webui/pull/24556) Works for me. Thx.

GiteaMirror commented

https://github.com/open-webui/open-webui/pull/24556/changes#diff-c5a084a65b46fbba7f2b0916c5ca4e5b3435eef28bc533e60c53ae85aeb1da4bR903

@Classic298 commented on GitHub (May 11, 2026):

@Ghosterme-dev in case you didn't notice, i deleted your comment multiple times now from this and other issues. You copy pasted the same comment everywhere, and it's AI Slop. The "root cause" is not the root cause and the line you identified at being at fault/needing changes is not actually the line that needs changes.

this here is what actually needs a fix.

Please don't copy paste the same answer on multiple issues, that is spamming - and even less so when it's wrong information. Thank you.

@Classic298 commented on GitHub (May 11, 2026): @Ghosterme-dev in case you didn't notice, i deleted your comment multiple times now from this and other issues. You copy pasted the same comment everywhere, and it's AI Slop. The "root cause" is not the root cause and the line you identified at being at fault/needing changes is not actually the line that needs changes. https://github.com/open-webui/open-webui/pull/24556/changes#diff-c5a084a65b46fbba7f2b0916c5ca4e5b3435eef28bc533e60c53ae85aeb1da4bR903 this here is what actually needs a fix. Please don't copy paste the same answer on multiple issues, that is spamming - and even less so when it's wrong information. Thank you.

GiteaMirror commented

@Ghosterme-dev commented on GitHub (May 11, 2026):

Sorry for the confusion. I wasn't aware that you deleted, as it said only bot. I thought the deletion was because the cases were already closed.

Only wanted to contribute your development.

However, I only had AI generate the layout, not the content. For some reason, though, the fix seems to have worked for me, so I wanted to let you know.
In any case, in the future I’ll be more careful with how I phrase things regarding the root cause.

@Ghosterme-dev commented on GitHub (May 11, 2026): Sorry for the confusion. I wasn't aware that you deleted, as it said only bot. I thought the deletion was because the cases were already closed. Only wanted to contribute your development. However, I only had AI generate the layout, not the content. For some reason, though, the fix seems to have worked for me, so I wanted to let you know. In any case, in the future I’ll be more careful with how I phrase things regarding the root cause.

GiteaMirror commented

2026-05-13 07:48:07 -05:00

@gaby commented on GitHub (May 11, 2026):

@Classic298 @tjbck It would be beneficial for Open-WebUI to release "rc" (release candidate) versions before a full release. Lately, releases have included both breaking bugs and database migrations.

@gaby commented on GitHub (May 11, 2026): @Classic298 @tjbck It would be beneficial for Open-WebUI to release "rc" (release candidate) versions before a full release. Lately, releases have included both breaking bugs and database migrations.

GiteaMirror commented

@Classic298 commented on GitHub (May 11, 2026):

That's the dev branch. The dev branch is the release candidate. Everything that gets merged into dev basically has a 99.9% chance of making it into the next version. It practically never happens that something gets reverted on the dev branch - especially not db migrations

And what's the issue with database migrations being in releases? We specifically warn about it in the release notes on top and on the bottom in the changed section

@Classic298 commented on GitHub (May 11, 2026): That's the dev branch. The dev branch is the release candidate. Everything that gets merged into dev basically has a 99.9% chance of making it into the next version. It practically never happens that something gets reverted on the dev branch - especially not db migrations And what's the issue with database migrations being in releases? We specifically warn about it in the release notes on top and on the bottom in the changed section

GiteaMirror commented

2026-05-13 07:48:07 -05:00

@Classic298 commented on GitHub (May 11, 2026):

We have said many times on reddit/discord and here that we would appreciate if people can help test the dev branch more.

Testing environments, development environments, companies deploying the dev branch on a test server to test out new features and prepare for a new version etc.

If there'd be dedicated release candidate versions i am not sure that would improve at all because why would they start using rc versions if they are already not trying out the dev branch.

@Classic298 commented on GitHub (May 11, 2026): We have said many times on reddit/discord and here that we would appreciate if people can help test the dev branch more. Testing environments, development environments, companies deploying the dev branch on a test server to test out new features and prepare for a new version etc. If there'd be dedicated release candidate versions i am not sure that would improve at all because why would they start using rc versions if they are already not trying out the dev branch.

GiteaMirror commented

2026-05-13 07:48:07 -05:00

@gaby commented on GitHub (May 11, 2026):

Are there docker images for the dev branch being published?

@gaby commented on GitHub (May 11, 2026): Are there docker images for the `dev` branch being published?

GiteaMirror commented

2026-05-13 07:48:08 -05:00

@Classic298 commented on GitHub (May 11, 2026):

Yes. Every single commit gets a tagged docker image and if you pull just the dev image you always get the latest commit of the dev branch

@Classic298 commented on GitHub (May 11, 2026): Yes. Every single commit gets a tagged docker image and if you pull just the dev image you always get the latest commit of the dev branch

GiteaMirror commented

2026-05-13 07:48:08 -05:00

@Classic298 commented on GitHub (May 11, 2026):

So every commit to dev, unless the build fails - in that case no tag is created - gets it's own tagged docker image with the sha being the identifier for that image, so you can even pin it to a specific commit if you like.

And the bare :dev tag always points to the latest commit on the dev branch

DB Migrations have, if i remember correctly, never been reverted on the dev branch.
And very large features are typically merged in one go. Tim creates dedicated large PRs for that and merges them into dev in one go - once that new feature is done.

I use dev privately, exclusively. For development but also for personal use. In my org we also have a dedicated testing environment with latest dev always deployed for testing new features and .. again: development.

I have caught minor not-ideal features before on dev branches, which helped us fix it before it shipped in a new version.

But bugs like this - I would never catch them because simply I do not use Open WebUI as an API proxy and this bug only affects that usecase.

WE ARE working on a full test suite with end-to-end tests and automated tests. And you can be sure that this one here got integrated yesterday, to cover an API-only chat completion flow. But before that entire test suite becomes really useful, a couple of months will have to pass where we slowly build and grow the test suite into hundreds of tests.

This doesn't mean we will never have regressions again, but it should help with reducing recurring regressions.

@Classic298 commented on GitHub (May 11, 2026): So every commit to dev, unless the build fails - in that case no tag is created - gets it's own tagged docker image with the sha being the identifier for that image, so you can even pin it to a specific commit if you like. And the bare :dev tag always points to the latest commit on the dev branch DB Migrations have, if i remember correctly, never been reverted on the dev branch. And very large features are typically merged in one go. Tim creates dedicated large PRs for that and merges them into dev in one go - once that new feature is done. I use dev privately, exclusively. For development but also for personal use. In my org we also have a dedicated testing environment with latest dev always deployed for testing new features and .. again: development. I have caught minor not-ideal features before on dev branches, which helped us fix it before it shipped in a new version. But bugs like this - I would never catch them because simply I do not use Open WebUI as an API proxy and this bug only affects that usecase. WE ARE working on a full test suite with end-to-end tests and automated tests. And you can be sure that this one here got integrated yesterday, to cover an API-only chat completion flow. But before that entire test suite becomes really useful, a couple of months will have to pass where we slowly build and grow the test suite into hundreds of tests. This doesn't mean we will never have regressions again, but it should help with reducing recurring regressions.

GiteaMirror commented

2026-05-13 07:48:08 -05:00

@Classic298 commented on GitHub (May 11, 2026):

And if not obvious - i encourage everyone here to use the dev branch.

If you do not want to risk your real data, then use it as a second environment only. If you are a company: set up a small (weak) VPS and install bare dev there and use it for development, testing and experimenting. If you catch anything that is out of the ordinary: great! Report it to us here so we can fix it while that bug is still in dev. We will be extremely happy if you do so.

In fact, this is the single thing you can do that has immense positive impact for Open WebUI.
Many PRs cannot be merged due to code quality, scope, atomicity or other reasons.
A well written bug report for a bug you found on the dev branch is GOLD.

If anyone needs a guide

https://docs.openwebui.com/getting-started/advanced-topics/development here is a guide how to manually set up a development environment
To use the dev branch, either set up the development environment as outlined in the docs, or for docker, just use the ghcr.io/open-webui/open-webui:dev tag

If you want a tagged version specific to one commit:

Just use the shortened commit hash and use that as tag as shown here in the image, which would result in, for example docker pull ghcr.io/open-webui/open-webui:git-41b48b5

@Classic298 commented on GitHub (May 11, 2026): And if not obvious - i encourage everyone here to use the dev branch. If you do not want to risk your real data, then use it as a second environment only. If you are a company: set up a small (weak) VPS and install bare dev there and use it for development, testing and experimenting. If you catch anything that is out of the ordinary: great! Report it to us here so we can fix it while that bug is still in dev. We will be extremely happy if you do so. In fact, this is the single thing you can do that has immense positive impact for Open WebUI. Many PRs cannot be merged due to code quality, scope, atomicity or other reasons. <ins>**A well written bug report for a bug you found on the dev branch is GOLD.**</ins> If anyone needs a guide - https://docs.openwebui.com/getting-started/advanced-topics/development here is a guide how to manually set up a development environment - To use the dev branch, either set up the development environment as outlined in the docs, or for docker, just use the `ghcr.io/open-webui/open-webui:dev` tag If you want a tagged version specific to one commit: <img width="1304" height="713" alt="Image" src="https://github.com/user-attachments/assets/6314cfd1-dceb-4714-81af-6c2bddb05e21" /> <img width="1506" height="774" alt="Image" src="https://github.com/user-attachments/assets/e933ba4e-d069-4223-8570-0d30a8b12177" /> Just use the shortened commit hash and use that as tag as shown here in the image, which would result in, for example `docker pull ghcr.io/open-webui/open-webui:git-41b48b5`

GiteaMirror commented

2026-05-13 07:48:09 -05:00

@alexlach commented on GitHub (May 12, 2026):

If anyone needs a workaround while staying 0.9.5, you can pass a dummy chat_id in the payload like this:

{
    "model": "gpt-5.5",
    "messages": [
        {
            "role": "user",
            "content": [{"type": "text", "text": prompt}],
        },
    ],
    "chat_id": "test",
}

@alexlach commented on GitHub (May 12, 2026): If anyone needs a workaround while staying 0.9.5, you can pass a dummy chat_id in the payload like this: ``` { "model": "gpt-5.5", "messages": [ { "role": "user", "content": [{"type": "text", "text": prompt}], }, ], "chat_id": "test", } ```

GiteaMirror commented

@moras-p commented on GitHub (May 12, 2026):

If anyone needs a workaround while staying 0.9.5, you can pass a dummy chat_id in the payload like this:
{
    "model": "gpt-5.5",
    "messages": [
        {
            "role": "user",
            "content": [{"type": "text", "text": prompt}],
        },
    ],
    "chat_id": "test",
}

For a quick fix, request with "chat_id": "" still fails for me, but "chat_id": "" does work.

@moras-p commented on GitHub (May 12, 2026): > If anyone needs a workaround while staying 0.9.5, you can pass a dummy chat_id in the payload like this: > > ``` > { > "model": "gpt-5.5", > "messages": [ > { > "role": "user", > "content": [{"type": "text", "text": prompt}], > }, > ], > "chat_id": "test", > } > ``` For a quick fix, request with "chat_id": "<any string>" still fails for me, but "chat_id": "" does work.

GiteaMirror commented

@Classic298 commented on GitHub (May 12, 2026):

The quick fix has been documented above by me. There's an open PR. it's a single line edit, in fact, just two characters need to get changed then it works again. Use that as the primary fix.

@Classic298 commented on GitHub (May 12, 2026): The quick fix has been documented above by me. There's an open PR. it's a single line edit, in fact, just two characters need to get changed then it works again. Use that as the primary fix.

GiteaMirror commented

@kaac5 commented on GitHub (May 13, 2026):

When can this bug be fixed?

@kaac5 commented on GitHub (May 13, 2026): When can this bug be fixed?

GiteaMirror commented