github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-11 00:04:08 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: Unsupported "keep_alive" parameter added to OpenAI payload if set in user settings #5399

New Issue
Closed
opened 2025-11-11 16:19:56 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-11 16:19:56 -06:00
Owner
Copy Link

Originally created by @hemzet on GitHub (May 30, 2025).

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

0.6.13

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

No response

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

Setting has no effect if not supported by an api - or parameter not applied to api call if not supported.

Actual Behavior

If the parameter "Keep Alive" is set in a user setting and any OpenAI model (e.g. GPT-4o) is used, the model returns an error:
400: Unknown parameter: 'keep_alive'

Steps to Reproduce

  1. Open user settings
  2. Change Keep Alive from Default to any value
  3. Start a chat using an OpenAI model (eg. ChatGPT-4o)

Logs & Screenshots

400: Unknown parameter: 'keep_alive'

Additional Information

No response

Originally created by @hemzet on GitHub (May 30, 2025). ### 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 0.6.13 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) _No response_ ### 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 Setting has no effect if not supported by an api - or parameter not applied to api call if not supported. ### Actual Behavior If the parameter "Keep Alive" is set in a user setting and any OpenAI model (e.g. GPT-4o) is used, the model returns an error: `400: Unknown parameter: 'keep_alive'` ### Steps to Reproduce 1. Open user settings 2. Change Keep Alive from Default to any value 3. Start a chat using an OpenAI model (eg. ChatGPT-4o) ### Logs & Screenshots `400: Unknown parameter: 'keep_alive'` ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:19:56 -06:00
GiteaMirror commented 2025-11-11 16:19:57 -06:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (May 30, 2025):

addressed, https://github.com/open-webui/open-webui/discussions/14515#discussioncomment-13314924

@i0ntempest's suggestion could be the solution here, but not entirely convinced if that'd be the best approach. Open to suggestions here.

#14479 (comment)

@rgaricano commented on GitHub (May 30, 2025): addressed, https://github.com/open-webui/open-webui/discussions/14515#discussioncomment-13314924 > @i0ntempest's suggestion could be the solution here, but not entirely convinced if that'd be the best approach. Open to suggestions here. > > [#14479 (comment)](https://github.com/open-webui/open-webui/issues/14479#issuecomment-2920411978)
GiteaMirror commented 2025-11-11 16:19:58 -06:00
Author
Owner
Copy Link

@hemzet commented on GitHub (May 30, 2025):

addressed, #14515 (comment)

@i0ntempest's suggestion could be the solution here, but not entirely convinced if that'd be the best approach. Open to suggestions here.
#14479 (comment)

Thanks for sharing. A toggle per model and parameter leads to bad user experience. Adding a toggle for each configured api and parameter requires admin privilege, wouldn't add to user experience either.

If (some) parameters are valid for Ollama only, why not preventing those from being added to the api call for OpenAPI calls?

@hemzet commented on GitHub (May 30, 2025): > addressed, [#14515 (comment)](https://github.com/open-webui/open-webui/discussions/14515#discussioncomment-13314924) > > > [@i0ntempest](https://github.com/i0ntempest)'s suggestion could be the solution here, but not entirely convinced if that'd be the best approach. Open to suggestions here. > > [#14479 (comment)](https://github.com/open-webui/open-webui/issues/14479#issuecomment-2920411978) Thanks for sharing. A toggle per model and parameter leads to bad user experience. Adding a toggle for each configured api and parameter requires admin privilege, wouldn't add to user experience either. If (some) parameters are valid for Ollama only, why not preventing those from being added to the api call for OpenAPI calls?
GiteaMirror commented 2025-11-11 16:19:58 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 31, 2025):

Because some OpenAI compatible endpoint providers also use the exact same parameters.

@tjbck commented on GitHub (May 31, 2025): Because some OpenAI compatible endpoint providers also use the exact same parameters.
GiteaMirror commented 2025-11-11 16:19:58 -06:00
Author
Owner
Copy Link

@KyleF0X commented on GitHub (Jun 1, 2025):

Yeh i just noticed this when trying to use o4-mini API

Image

@KyleF0X commented on GitHub (Jun 1, 2025): Yeh i just noticed this when trying to use o4-mini API ![Image](https://github.com/user-attachments/assets/33e21f1a-85ac-450c-94ca-36771ea3917b)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5399
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?