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
Set OpenAI compatible TTS url in admin settings --> audio.
Successfully save.
TTS server is offline in such a manner where it appears on the network but refuses to respond.
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).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13028
### 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 2026-05-13 03:21:00 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dogarrowtype on GitHub (Apr 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13028
Check Existing Issues
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
README.md.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
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.