Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

OpenWebUI

80 Topics 736 Posts
  • OpenWebUI - Package Updates

    Pinned Locked
    207
    1 Votes
    207 Posts
    167k Views
    Package UpdatesP
    [3.5.0] Update open-webui to 0.11.0 Full Changelog Database Migrations: This release includes database schema changes; we strongly recommend backing up your database and all associated data before upgrading in production environments. If you are running a multi-worker, multi-server, or load-balanced deployment, all instances must be updated simultaneously, rolling updates are not supported and will cause application failures due to schema incompatibility. Security Advisory: This release includes security and access-control fixes. We recommend updating production deployments at your earliest convenience. Not all security fixes in this version may be enumerated in the fixed section. Some may be withheld for a short time to give administrators time to upgrade. Advisories Redesigned interface. Open WebUI has been visually rebuilt from the ground up. All aspects of the User Interface, from the chat view to the admin panel. Now with a narrower conversation column, lighter typography, tidier spacing, consistent menus and dropdowns, clearly outlined text boxes, and settings rearranged. Sub-agents. Administrators can now enable sub-agents, which let a model hand parts of a task to background helper agents that run their own tool-driven conversations and report results back into the chat, tuned through new "ENABLE_SUBAGENTS", concurrency, iteration, and system-prompt settings. The "python-jose" library is no longer installed. Nothing in Open WebUI imports it anymore, so it and the two packages it pulled in have been dropped from the image, and any tool or function that imports it directly now needs to install it itself. #27444 Usage now reports the latest call separately. In a response's usage block, "prompt_tokens" and "completion_tokens" now carry the counts from the most recent model call rather than the running total, while "input_tokens", "output_tokens" and "total_tokens" stay cumulative, so anything reading the first pair for billing should read the second set instead. Administrators no longer reach other people's automations. Viewing, editing, running and deleting an automation is now limited to the person who created it, so an administrator with a link to someone else's automation is refused rather than allowed through. Storage emulator no longer bundled. The optional Google Cloud Storage emulator is no longer installed as part of the full package, so anyone who relied on it for local storage testing now needs to install "gcp-storage-emulator" themselves. Blank messages on Safari. Assistant responses no longer render as empty in Safari and on iPhone and iPad, where a browser painting bug left on-screen messages unpainted. #26805, #26712, #26844 Terminal file preview isolation. Previewing an HTML file in the system terminal now runs it in an isolated context by default, closing a cross-site scripting hole that could expose your login session or, for privileged accounts, run code on the server. #26907
  • Since Package Version [3.4.0] - Empty Responses from Mistral?

    5
    0 Votes
    5 Posts
    193 Views
    dsp76D
    No I directly used models without router. After a manual restart of OpenWebUI (it was automatically updated), the problem was gone. No issue anymore.
  • ETA for GPU support? Could we contribute to help it along?

    27
    4 Votes
    27 Posts
    7k Views
    L
    Hello all. We have been doing a deep recce on what GPU support would take in 2026, and we think the landscape has shifted enough since it was last assessed to be worth a fresh summary. Posting the salient parts with links, in case it helps the team and anyone experimenting. The "patched docker" requirement appears to be gone. The last assessment (here) noted that NVIDIA seemed to need a patched Docker while Cloudron relies on the official Ubuntu packages. That was true for years, the old nvidia-docker stack did require a custom runtime, but the Container Device Interface (CDI) has since removed the requirement: Docker Engine supports CDI natively since 25.0 and enables it by default in the 28.x series (the CNCF CDI docs say from 28.2.0, the Docker docs say 28.3.0). The official Ubuntu 24.04 docker.io package now carries 28.2.2 in noble-updates and 27.5.1 in the security pocket (Launchpad). So the stock Ubuntu packages already have CDI: default-on at 28.2.2, or a one-line daemon.json feature flag on 27.5.1. With CDI there is no custom runtime and no default-runtime change. The host needs the NVIDIA driver plus nvidia-container-toolkit, which provides nvidia-ctk cdi generate and now ships an nvidia-cdi-refresh service that regenerates the spec automatically when the driver changes (NVIDIA docs, releases, currently 1.19.1). Containers then receive GPUs via --device nvidia.com/gpu=all, which maps to an ordinary device request in the Engine API. Quick check on any host: docker version --format '{{.Server.Version}}' docker info | grep -iA2 cdi # on a GPU host with a generated spec: docker run --rm --device nvidia.com/gpu=all ubuntu:24.04 nvidia-smi -L The platform change may be smaller than expected. The manifest already has the vaapi capability passing /dev/dri. An equivalent capability, or a per-app admin toggle, that appends a CDI device request at container create looks like most of the change, and it can no-op silently when no CDI spec exists, so GPU-less servers are unaffected. AMD compute (ROCm) would only additionally need /dev/kfd; Intel and AMD media is arguably covered by vaapi already. Two caveats from the research: The reliability risk has moved from Docker to the driver lifecycle. The recent report of a server left unbootable after a driver update is the failure class to design against: the -server LTS driver branch, apt holds, and a deliberate upgrade procedure rather than unattended driver updates. The container toolkit had several critical escape CVEs through 2024 and 2025, mostly in the legacy hook path. CDI mode plus a current toolkit is the safer default, and GPU servers are best treated as trusted-workload machines. On the testing-hardware constraint mentioned previously: hardware offers have been made in this thread before, and we are happy to run validation on real NVIDIA hardware and share results.
  • redis errors after updating Open WebUI from 0.9.6 to 0.10.1

    redis openwebui
    6
    0 Votes
    6 Posts
    236 Views
    jamesJ
    This is a regression of @openwebui version 0.10.1 and is already fixed by version 0.10.2. With the upcoming release of 0.10.2 this is fixed.
  • V0.9.2 is available - fixes critical bug

    2
    2 Votes
    2 Posts
    259 Views
    nebulonN
    new package is out
  • Critical Bug in OpenWebUI 0.9.0 from Mainstream

    2
    1 Votes
    2 Posts
    315 Views
    nebulonN
    The new package update is already in our release pipeline yes
  • Latest OpenWebUI with Openterminal

    4
    1 Votes
    4 Posts
    749 Views
    firmansiF
    @charlesnw I am running open terminal but in another container, i think it's best to maintain Open WebUI with original package
  • Conduit - OpenWebUi Client for mobile devices

    4
    2 Votes
    4 Posts
    1k Views
    timconsidineT
    @charlesnw [image: 1773858777076-screenshot-2026-03-18-at-18.32.36-resized.png] you should invite some friends !
  • 0 Votes
    8 Posts
    1k Views
    firmansiF
    @nebulon it works...thanks cloudron team for fast update
  • Problem updating to 3.0.5

    8
    0 Votes
    8 Posts
    2k Views
    S
    Newest package that ships Open WebUI 0.7.2 resolved this
  • "Ollama: Network Problem" Error in OpenWebUI

    3
    1 Votes
    3 Posts
    2k Views
    timconsidineT
    @omnichannel I’m using openwebui and ollama apps installed in the same Cloudron instance. In openwebui Admin settings, under Connections, I am using similar to what you have. Server connection is verified.
  • Issues with 60 seconds timeout (unsure if related to Ollama or OpenwebUI)

    Solved ollama timeout
    6
    0 Votes
    6 Posts
    3k Views
    nebulonN
    the new package now disables the max body check for the nginx within the app. I couldn't quite reproduce the issue in my setup, not sure how you ended up with such big queries, but hopefully it fixes your case.
  • how to configure Ollama in OpenWebUI

    8
    1
    1 Votes
    8 Posts
    2k Views
    jamesJ
    Hello @harryz There is your problem. The model requires 8.7 GB and your system only has 7.9 GB of free memory left.
  • Install Additional Python Module for OpenWebUI

    7
    1 Votes
    7 Posts
    4k Views
    N
    Installation of additional packages would be great! Would a quick fix be to make the directory "/app/code/venv/lib/python3.12/site-packages/" writable in the cloudron app (eg. symlink to a /app/data/site-packages directory)?
  • Update OpenWebUI without Ollama

    8
    1 Votes
    8 Posts
    3k Views
    firmansiF
    @girish ya, i think this is a good approach because in real use case, I think most people prefer to run inference models not in the same machine with openWebUI instance. OpenWebUI is good enough bundled with chromadb , sql lite or postgressql database and redis as one package and the inference models (including ollama) running in different servers.
  • Openwebui V0.6.30

    3
    1 Votes
    3 Posts
    1k Views
    J
    Looks like this was released on Sep 23
  • Anyone successfully installed a fileserver MCP?

    mcp mcp proxy
    8
    2 Votes
    8 Posts
    2k Views
    D
    @micmc all credit to the author of the repository
  • Activating OIDC on older install.

    Solved
    4
    1
    0 Votes
    4 Posts
    1k Views
    D
    Thanks everyone for your assistance
  • Integrated Redis

    10
    2 Votes
    10 Posts
    2k Views
    jamesJ
    Hello @firmansi Thanks for the feedback. I was only able to confirm it was working with a debug startup. So it is very good to read from you that it is in fact working.
  • 0 Votes
    8 Posts
    3k Views
    jfrereJ
    It depend on the PDF itself I guess. I've uploaded one, and got a new error message. [image: 1753521763160-c7c88ba2-416b-499e-825b-64ffcb747c7c-image.png]