mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 02:48:13 -05:00
[GH-ISSUE #4087] New config sidebar dont save selected values and overwrite system wide config. #13492
Reference in New Issue
Block a user
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?
Originally created by @luisbrandao on GitHub (Jul 24, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/4087
Bug Report
Description
Bug Summary:



The new "sidebar" chat controls don't save the config, it is lost on page refresh.
If they are set to default, it get the web-ui default (for example, 2048 of context) and ignore system wide config:
Steps to Reproduce:
Get in any chat, fiddle with the sidebar controls and then refresh.
Expected Behavior:
Default value either keep between refreshes or at least fall back to system default.
Actual Behavior:
Config are lost between refreshes.
Environment
Open WebUI Version: 0.3.10
Ollama (if applicable): 0.2.8
Operating System: [Rocky8/9]
Browser (if applicable): [Brave browser]
Reproduction Details
Logs and Screenshots
Browser Console Logs:

no log generated when config is fiddle with. There are somethings on reload. They dont prevent webui from working
Docker Container Logs:
no log generated when config is fiddle with. (no request sent from browser to webui)
Installation Method
Docker with httpd reverse proxy and https.
@justinh-rahb commented on GitHub (Jul 24, 2024):
It's not intended for these values to be saved, they're for the session you're currently in. As such it also makes sense for them to override the global values as determined by consensus in the original issue/PR. I have not observed that any parameters are sent at all if everything is
Defaulteverywhere.All

Default:Setting

num_ctx:@luisbrandao commented on GitHub (Jul 24, 2024):
I think there is something not working well while using the reverse proxy.
I just tried to connect using the direct container ip and the behavior is way more consistent.