mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-11 08:15:00 -05:00
0.3.7: Browser Language Detection - Ignores English setting in Chrome #1408
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 @brunocerq on GitHub (Jun 30, 2024).
Bug Report
Description
Bug Summary:
After updating to 0.3.7 the UI is presented in the browser language ignoring the language option set in settings if the language chosen it English (US and GB).
Steps to Reproduce:
Update to 0.3.7 running on a machine with browser language different from the UI language settings.
Expected Behavior:
Expected the UI to be displayed with the language set in settings (Portuguese), in my case I want the UI to be presented in English (US) but even with the language setting to English the UI is always showed in Portuguese (My browser language setting).
Actual Behavior:
The UI is being presented in the browser language (Portuguese) whenever I choose English (US) or English (GB) in settings, it DOES change for any other language other then English.
Environment
Open WebUI Version: [0.3.7]
Ollama (if applicable): [0.1.47]
Operating System: [Windows 11/Docker Desktop]
Browser (if applicable): [Chrome 126.0.6478.127]
Reproduction Details
Confirmation:
Logs and Screenshots
Screenshots (if applicable):

[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Docker Desktop]
Additional Information
Cookies deleted in chrome, behaviour is the same, in Firefox it's working fine.
@brunocerq commented on GitHub (Jun 30, 2024):
@PiMaV commented on GitHub (Jun 30, 2024):
I can confirm this issue on:
Ubuntu using Docker with webui 0.3.7.
The problem occurs when accessing the UI via Windows 11 and Opera with local German settings.
@agusmdev commented on GitHub (Jun 30, 2024):
Same happening to me, can't make it work in english
@tjbck commented on GitHub (Jun 30, 2024):
Should be fixed with the latest main, let me know if the issue persists!