mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #9960] Kokoro-JS TTS Feature Missing in Open WebUI v0.5.11 #54378
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 @latent-variable on GitHub (Feb 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9960
Bug Report
Installation Method
Docker (:main tag)
Environment
• Open WebUI Version: v0.5.11
• Ollama (if applicable): v0.5.9
• Operating System: macOS Big Sur
• Browser (if applicable): Chrome
Confirmation:
• I have read and followed all the instructions provided in the README.md.
• I am on the latest version of both Open WebUI and Ollama.
• I have provided the exact steps to reproduce the bug in the “Steps to Reproduce” section below.
Expected Behavior:
The Kokoro-JS TTS Support feature should be available and functional in the UI after upgrading to version v0.5.11.
Actual Behavior:
The Kokoro-JS TTS Support option is not available in the UI, even after updating to Open WebUI v0.5.11.
Description
Bug Summary:
After upgrading to Open WebUI v0.5.11, the newly announced Kokoro-JS TTS Support is not available. There is no option in the UI, settings, or relevant configurations to enable or access it.
Reproduction Details
Steps to Reproduce:
1. Pull and run Open WebUI v0.5.11 via Docker.
2. Check the UI for the Kokoro-JS TTS Support option.
3. Attempt to enable or use the TTS feature.
4. Observe that it is missing.
Logs and Screenshots
Screenshots/Screen Recordings (if applicable):
Additional Information
• No errors related to Kokoro-JS appear in the browser console or Docker logs.
• Confirmed that I am running the correct version (v0.5.11).
• I have cleared the browser cache and restarted the application.
Note
Please let me know if any additional setup is required for this feature or if there are any known issues with its availability in v0.5.11.
@tjbck commented on GitHub (Feb 14, 2025):
Only available from the individual user settings.