issue: Crash in admin settings when TTS server refuses to respond #4899

Closed
opened 2025-11-11 16:06:00 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @dogarrowtype on GitHub (Apr 18, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

v0.6.5

Ollama Version (if applicable)

No response

Operating System

Arch Linux

Browser (if applicable)

Firefox 137

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 listed steps to reproduce the bug in detail.

Expected Behavior

When the TTS server is unavailable, it should fail gracefully and not take down the whole open-webui server.

Actual Behavior

Open-webui becomes unresponsive and must be restarted, when the OpenAI-compatible TTS server fails to send a response to the expected endpoints.

Steps to Reproduce

  1. Set OpenAI compatible TTS url in admin settings --> audio.
  2. Successfully save.
  3. TTS server is offline in such a manner where it appears on the network but refuses to respond.
  4. Open-webui stalls and becomes unresponsive, and must be terminated and restarted.

Logs & Screenshots

I have checked the logs and there is no relevant error message. It simply stalls without warning.

Additional Information

This bug left me unable to access the audio settings menu in the admin panel to change to another server. To restore TTS, I had to download the config.json settings backup, edit the TTS server to another IP manually, then reupload the modified config.json.
The crash will happen immediately when switching to the audio tab of the admin panel if the TTS server is unresponsive.

Originally created by @dogarrowtype on GitHub (Apr 18, 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 Pip Install ### Open WebUI Version v0.6.5 ### Ollama Version (if applicable) _No response_ ### Operating System Arch Linux ### Browser (if applicable) Firefox 137 ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior When the TTS server is unavailable, it should fail gracefully and not take down the whole open-webui server. ### Actual Behavior Open-webui becomes unresponsive and must be restarted, when the OpenAI-compatible TTS server fails to send a response to the expected endpoints. ### Steps to Reproduce 1. Set OpenAI compatible TTS url in admin settings --> audio. 2. Successfully save. 3. TTS server is offline in such a manner where it appears on the network but refuses to respond. 4. Open-webui stalls and becomes unresponsive, and must be terminated and restarted. ### Logs & Screenshots I have checked the logs and there is no relevant error message. It simply stalls without warning. ### Additional Information This bug left me unable to access the audio settings menu in the admin panel to change to another server. To restore TTS, I had to download the config.json settings backup, edit the TTS server to another IP manually, then reupload the modified config.json. The crash will happen immediately when switching to the audio tab of the admin panel if the TTS server is unresponsive.
GiteaMirror added the bug label 2025-11-11 16:06:00 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4899