Replies: 1 comment 4 replies
-
Update: Upon further inspection of the logs, I identified that the error was a I confirmed that everything works correctly when directly accessing the website without a proxy. To fix the problem, I modified the Nginx proxy configuration as follows: Solution: proxy_connect_timeout 3000;
proxy_send_timeout 3000;
proxy_read_timeout 3000;
send_timeout 3000; This configuration increases the timeout to 3000 seconds (50 minutes). But I have also noticed another problem with using a proxy. The typewriter effect where the Ollama server responds with tokens progressively is not functioning as expected. Instead of seeing a smooth, incremental display of text, there's a delay followed by a sudden chunk of multiple words. This is observed in the logs where multiple responses are received together, suggesting that the proxy is bundling the responses and sending them in batches. The problem is caused by Nginx's default behavior of buffering proxied responses. To achieve the typewriter effect, buffering needs to be disabled so that responses are streamed immediately as they are received from the backend server. Solution: # Disable buffering
proxy_buffering off;
proxy_cache off; |
Beta Was this translation helpful? Give feedback.
-
Bug Report
Description
Bug Summary:
Image generation on cpu times out.
Steps to Reproduce:
Expected Behavior:
Wait a bit longer or provide a setting to control the timeout.
Actual Behavior:
It just times out.
Environment
Open WebUI Version: v0.1.124
Operating System: Ubuntu Server
Browser (if applicable): Chrome
Reproduction Details
Confirmation:
Installation Method
Installed through Docker.
Additional Information
This issue is not entirely similar to #1611 but I believe a fix could solve both of them since they are related to timeouts
Beta Was this translation helpful? Give feedback.
All reactions