openwebui-clear-embedding-cache

Clear miscached embedding snapshots in Open-WebUI containers to resolve 500 errors.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/crycriM/hermes-skills --skill openwebui-clear-embedding-cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openwebui-clear-embedding-cache
Source: https://github.com/crycriM/hermes-skills/tree/main/openwebui-clear-embedding-cache
Command: npx skills add https://github.com/crycriM/hermes-skills --skill openwebui-clear-embedding-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clears a miscached Open-WebUI embedding model snapshot that causes HTTP 500 errors due to architecture mismatch, ensuring a fresh, compatible model is downloaded on restart.

Core Features & Use Cases

  • Cache remediation: Identify and delete misaligned embedding snapshots to restore normal startup.
  • Automatic recovery: Restart the Open-WebUI container to re-download a compatible model.
  • Operational validation: Monitor logs for "Loading weights" and verify the UI responds to prompts.

Quick Start

Run the provided script to clear the embedding cache and restart the Open-WebUI container, then verify that the model re-downloads.

Frequently Asked Questions about openwebui-clear-embedding-cache

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Open-WebUI return 500 errors after startup when logs show architecture mismatch warnings?

Open-WebUI returns 500 errors due to a miscached embedding model snapshot with an incompatible architecture. Deleting the problematic snapshot and restarting triggers a fresh download of a compatible model, resolving the startup failure.

How do I clear the embedding cache in an Open-WebUI docker container?

To clear the embedding cache in an Open-WebUI docker container, access the container, locate the correct cache path, delete the misaligned embedding snapshot, and restart the container to automatically re-download the correct model.

Does clearing the Open-WebUI embedding cache require internet connectivity?

Yes, clearing the Open-WebUI embedding cache requires internet connectivity. After deleting the miscached snapshot, the container must connect to the internet to re-download a fresh, architecture-compatible embedding model during restart.

What is the best way to verify Open-WebUI recovered from an embedding architecture mismatch?

The best way to verify recovery from an embedding architecture mismatch is to monitor the Open-WebUI logs for 'Loading weights' messages and confirm the UI successfully responds to prompts after the container restarts.

When should I not delete the Open-WebUI embedding snapshot?

You should not delete the Open-WebUI embedding snapshot if you lack direct container access or internet connectivity, as the container needs internet to re-download the embedding model and restore normal UI functionality.