[GH-ISSUE #24554] issue: Open WebUI v0.9.5 Broken Completions API #107324

New Issue

GiteaMirror · 2026-05-18T06:06:17-05:00

GiteaMirror commented

2026-05-18 06:06:17 -05:00

Originally created by @xcjs on GitHub (May 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24554

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

v.0.9.5

Ollama Version (if applicable)

This applies to multiple backends.

Operating System

Windows 11 (Client)/Ubuntu 24.04 (Server)

Browser (if applicable)

N/A

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

I expect to continue to be able to use token-authenticated clients to access the completions API as I have before.

Actual Behavior

I now receive a 400 Bad Request response.

I primarily use OpenCode as a client, but also use Continue Dev in VSCode for autocomplete behavior. Both clients report the same error after the v0.9.5 update from v0.9.4

OpenCode:

Bad Request: {"detail":"'NoneType' object has no attribute 'startswith'"}

Continue Dev:

Continue Autocomplete Error: HTTP 400 Bad Request from https://{{Open WebUI domain}}/api/chat/completions {"detail":"'NoneType' object has no attribute 'startswith'"}

Steps to Reproduce

Upgrade to/install Open WebUI v0.9.5.
Enable token authentication.
Configure a client that utilizes the completions API.
Use the client.

Logs & Screenshots

OpenCode:

Continue Dev:

Removed screenshot that leaked domain information.

Additional Information

No response

Originally created by @xcjs on GitHub (May 10, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24554 ### 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 v.0.9.5 ### Ollama Version (if applicable) This applies to multiple backends. ### Operating System Windows 11 (Client)/Ubuntu 24.04 (Server) ### Browser (if applicable) N/A ### 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 I expect to continue to be able to use token-authenticated clients to access the completions API as I have before. ### Actual Behavior I now receive a `400 Bad Request` response. I primarily use OpenCode as a client, but also use Continue Dev in VSCode for autocomplete behavior. Both clients report the same error after the `v0.9.5` update from `v0.9.4` **OpenCode**: ```bash Bad Request: {"detail":"'NoneType' object has no attribute 'startswith'"} ``` **Continue Dev**: ```bash Continue Autocomplete Error: HTTP 400 Bad Request from https://{{Open WebUI domain}}/api/chat/completions {"detail":"'NoneType' object has no attribute 'startswith'"} ``` ### Steps to Reproduce 1. Upgrade to/install Open WebUI v0.9.5. 2. Enable token authentication. 3. Configure a client that utilizes the completions API. 4. Use the client. ### Logs & Screenshots **OpenCode**: <img width="743" height="65" alt="Image" src="https://github.com/user-attachments/assets/e4fd021c-25f2-4ce9-9aba-0cc595f53435" /> **Continue Dev**: Removed screenshot that leaked domain information. ### Additional Information _No response_

GiteaMirror added the bug label 2026-05-18 06:06:17 -05:00

GiteaMirror closed this issue

2026-05-18 06:06:20 -05:00

GiteaMirror commented

2026-05-18 06:06:22 -05:00

@owui-terminator[bot] commented on GitHub (May 10, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

🟣 #24550 bug: NoneType object has no attribute 'startswith' — all /api/v1/chat/completions calls return 400 (v0.9.5, direct connections)
This is the closest match: it reports the same v0.9.5 regression, the same exact 'NoneType' object has no attribute 'startswith' error, and the same 400 response on chat/completions for external API clients using token auth.
by ThefloorMiner
🟢 #24553 issue: /api/chat/completions runs into error
This open issue describes the same /api/chat/completions failure in v0.9.5 with the identical 'NoneType' object has no attribute 'startswith' error, so it is clearly the same bug family.
by tweinberger-lei · bug

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

@owui-terminator[bot] commented on GitHub (May 10, 2026):  🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#24550](https://github.com/open-webui/open-webui/issues/24550) **bug: NoneType object has no attribute 'startswith' — all /api/v1/chat/completions calls return 400 (v0.9.5, direct connections)** *This is the closest match: it reports the same v0.9.5 regression, the same exact `'NoneType' object has no attribute 'startswith'` error, and the same 400 response on chat/completions for external API clients using token auth.* *by ThefloorMiner* 2. 🟢 [#24553](https://github.com/open-webui/open-webui/issues/24553) **issue: /api/chat/completions runs into error** *This open issue describes the same `/api/chat/completions` failure in v0.9.5 with the identical `'NoneType' object has no attribute 'startswith'` error, so it is clearly the same bug family.* *by tweinberger-lei · `bug`* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.

GiteaMirror commented

2026-05-18 06:06:22 -05:00

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

https://github.com/open-webui/open-webui/issues/24553

@Classic298 commented on GitHub (May 10, 2026): https://github.com/open-webui/open-webui/issues/24553

GiteaMirror commented

2026-05-18 06:06:23 -05:00

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

@Classic298 Just saw that - sorry!

@xcjs commented on GitHub (May 10, 2026): @Classic298 Just saw that - sorry!

Sign in to join this conversation.