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 750 Posts
  • OpenWebUI - Package Updates

    Pinned Locked
    219
    1 Votes
    219 Posts
    200k Views
    Package UpdatesP
    [3.7.0] Update open-webui to 0.12.0 Full Changelog 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 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. IMPORTANT for Milvus and Milvus multitenancy users: back up your Milvus data before upgrading: On first start with "ENABLE_DB_MIGRATIONS" on (the default), every existing Milvus collection is copied in full into a new one holding its vectors, text and BM25 keyword index together, and Open WebUI only finishes starting once that is done, which can take hours for hundreds of gigabytes and needs free disk space for a second copy of your Milvus data. Nothing is re-embedded, and the originals are only dropped once every copy has succeeded. Back up first and avoid upgrading Milvus and Open WebUI on the same day. Hybrid search on Milvus needs Milvus 2.5 or newer; on older versions the migration is skipped and there is no native hybrid search. #31645, #31660 Realtime voice calls. Administrators can now switch Call mode in the Voice calls section of Audio settings from Standard to Realtime, so Voice mode talks through an OpenAI Realtime voice model (gpt-realtime-2.1-mini with the Marin voice by default) that handles small talk itself and hands real questions and tasks to the chat's selected model, with its conversation history and tools, before speaking the answer while the full reply appears in the chat. Commit, #5894 Two-factor sign-in. Administrators can require an authenticator app for every user under Admin Settings > Authentication, or with "ENABLE_MFA", so users set one up from a QR code on their next sign-in, get ten single-use recovery codes, and can later replace their authenticator or create new recovery codes in their account settings. Commit ENABLE_PLUGINS is the master switch. Setting "ENABLE_PLUGINS=false" now turns off every kind of plugin, including external OpenAPI, MCP and Open Terminal servers and personal direct connections, and overrides "ENABLE_TOOLS", "ENABLE_FUNCTIONS" and "ENABLE_TOOL_SERVERS"; all four need a restart to take effect. Commit, #31509 Arena models off by default. "ENABLE_EVALUATION_ARENA_MODELS" now defaults to off, so new installations no longer show the built-in arena model in the model selector; existing installations keep their current setting. Commit Revoked access ends live updates. Removing someone's access to a shared channel or a note, or deleting it, now also stops the live messages and edits their open sessions were still receiving from it. Commit Links no longer act on your behalf without asking. Opening Open WebUI from a link, including from another website or a hidden frame, can no longer act in your name unseen: a prompt given with "?q=" is only filled into the message box instead of being sent, loading web pages or videos with "load-url" or "youtube" and starting a voice call with "call=true" or "voice=true" now ask for confirmation first. Commit orjson on by default. "ENABLE_ORJSON" now defaults to on, and setting "ENABLE_ORJSON=false" switches back to the standard JSON encoder. #31616
  • Install Additional Python Module for OpenWebUI

    9
    1 Votes
    9 Posts
    5k Views
    jamesJ
    Hello @nckne The @openwebui app is complex and enabling users to install other python packages would add more complexity. Like mentioned before, you can customize the app yourself if you really need other python packages.
  • Since Package Version [3.4.0] - Empty Responses from Mistral?

    5
    0 Votes
    5 Posts
    452 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
    8k 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
    588 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
    383 Views
    nebulonN
    new package is out
  • Critical Bug in OpenWebUI 0.9.0 from Mainstream

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

    4
    1 Votes
    4 Posts
    1k 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
    2k Views
    timconsidineT
    @charlesnw [image: Screenshot 2026-03-18 at 18.32.36.png] you should invite some friends !
  • 0 Votes
    8 Posts
    2k 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
    3k 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
    3k 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.
  • 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
    3k 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
    3k 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: image.png]