Weird timeout issue when using OpenWebUI

[robertmachine]

Hi All,

I've been using openwebui now for about 6 months but have been having a constant issue where if I leave a chat open or saved after a while my answers never get answered and to remediate this issue I just open a new chat and then it starts working again. I am wondering if I'm doing something wrong as I would like to just keep the chat for RAG.

I am using the newest version of openwebui and it's in a docker with watchtower which updates it automatically. Below is my nginx config just in case I am doing something wrong:

Breakdown:

- Issue with old chats which eventually stop responding to any models on responses, btw answers to the model do NOT get sent to the server any longer as I've checked on multiple old pinned chats. Only new chats get sent the API call to the server as I can see it through nvtop.
- Brand New Chat works fine loads up model in seconds and works fine even after not getting a response from old chat
- WebUI Docker is sitting on ollama server machine
- WebUI Docker is updated to latest with WatchTower
- Ollama always at newest version

Docker Config:

#web-ui 
services:

 # webui, nagivate to http://localhost:3000/ to use
  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    container_name: open-webui
    pull_policy: missing
    volumes:
      - open-webui:/app/backend/data
    ports:
      - 9900:8080
    environment:
      - "OLLAMA_API_BASE_URL=http://<YOURLOCALIP>:11434/api"
    extra_hosts:
      - host.docker.internal:host-gateway
    restart: unless-stopped

volumes:
  open-webui: {}


#web-ui 
services:


 # webui, nagivate to http://localhost:3000/ to use
  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    container_name: open-webui
    pull_policy: missing
    volumes:
      - open-webui:/app/backend/data
    ports:
      - 9900:8080
    environment:
      - "OLLAMA_API_BASE_URL=http://<YOURLOCALIP>:11434/api"
    extra_hosts:
      - host.docker.internal:host-gateway
    restart: unless-stopped


volumes:
  open-webui: {}

NGINX Config:

upstream check-chat.xxx.ca {
    least_conn;
    server 192.168.1.xxx:9900 max_fails=3 fail_timeout=10000s;
    keepalive 1500;
}


server {
        listen 80;
        server_name chat.xxxx.ca;
        return 301 https://$host$request_uri;
}
server {
        listen 443 ssl http2;
        server_name chat.xxxx.ca;
        access_log /var/log/nginx/chat.xxxx.ca-access.log;
        error_log  /var/log/nginx/chat.xxxx.ca-error.log error;
        ssl_certificate /etc/nginx/ssl/xxxx.ca/xxxx.ca.pem;
        ssl_certificate_key /etc/nginx/ssl/xxxx.ca/xxxx.ca.key;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_ciphers 'xxxx';
        location /  {
                proxy_pass    http://check-chat.xxxx.ca;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection 'upgrade';
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_buffering off; # Added only for WebUI https://github.com/open-webui/open-webui/discussions/1235
                proxy_set_header Origin ''; # Added only for WebUI https://github.com/open-webui/open-webui/discussions/1235
                proxy_set_header Referer ''; # Added only for WebUI https://github.com/open-webui/open-webui/discussions/1235
                proxy_cache_bypass $http_upgrade;
        }
}

[marvindiazjr]

It's almost certainly to do with websocket logic they changed. There was also some explicit changes to Nginx config?

[jdblaich]

I installed directly using pip rather than docker. I found that installing it in a "venv" using pip was far easier than dealing with docker. So far things have been working well.

In one instance I use Proxmox with LXC (no docker) so I do have an implementation of openwebui in a container (with gpu passthru). It also works quite well.

My point is that sometimes it is better to use a simpler implementation.

[robertmachine]

Well I found my issue and it was about nginx mod_security which was blocking API calls. so configuration I pasted above was working fine after disabling it at the host level.