[GH-ISSUE #18600] issue: Pyodide Lockfile Version Mismatch - Solved #18649

New Issue

GiteaMirror · 2026-04-20T00:51:38-05:00

GiteaMirror commented

2026-04-20 00:51:38 -05:00

Originally created by @Grant-CP on GitHub (Oct 24, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18600

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.34

Ollama Version (if applicable)

N/A

Operating System

macOS Sonoma 15.7.1

Browser (if applicable)

Firefox

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When I run code in a python code block, I expect that it will run in pyodide. This was working in older versions of Open-Webui and is once again working, but was not working until I flushed my browser cache on one of my computers.

This bug happened on Firefox for MacOS but not Firefox for Windows, although that may not have been the deciding factor. My windows device was also accessing the Docker image directly via local port, while the MacOS computer was accessing via Cloudflare tunnel, although again not sure if that's relevant.

Actual Behavior

Pyodide on my Mac machine was giving me an "Execution Time Exceeded" message in the status message under the code block. All other Webui features were working fine

I decided to open up the browser log and saw

Lock file ABI version doesn't match Pyodide ABI version.
   lockfile version: 2024_0
   pyodide  version: 2025_0

After I cleared all local site data AND closed openwebui on my Mac device I was able to get my computer to load a fully new version of pyodide and I could run in my browser.

Steps to Reproduce

It's a little unclear exactly what caused it. In my mind there are three options.

Firefox for Mac didn't ask correctly for the new version of Pyodide's lockfile, but Firefox for Windows did.
There were some strange cache setting related to the Cloudflare Tunnel setup that made some things not cache correctly.
Updating the UI on the server side WHILE having the UI open on my mac computer somehow meant it didn't ask for all up-to-date files.

I'm using the most current version of Firefox - 144.0 on my Mac.

Logs & Screenshots

Relevant browser logs are:

Lock file ABI version doesn't match Pyodide ABI version.
   lockfile version: 2024_0
   pyodide  version: 2025_0

Additional Information

Mostly leaving this here to help other people troubleshoot in case they run into the same problem (I couldn't find an open issue mentioning pyodide in the repo). I also did a google search with my browser log snippet and came up with NOTHING even mildly related so I imagine some people would have a lot of trouble fixing this on their own.

My suggested fixes would be one of the following:

More descriptive error message on pyodide failure. Instead of saying "Execution Time Exceeded" when pyodide doesn't even load say "Pyodide error - Check Browser Console" or something of that sort.
Have the UI detect Pyodide lockfile version mismatch and force the browser to reload.
On pyodide failure of any kind, try a full flush and reload of pyodide and all associated files (but max once per 30 minutes or something)

I suspect that the true problem with Pyodide/WASM and caching is a result of them being newer technology (and me using the least supportive browser - Mac Firefox), so I imagine that fix 1 is the only reasonable one to maybe implement.

Originally created by @Grant-CP on GitHub (Oct 24, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18600 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.34 ### Ollama Version (if applicable) N/A ### Operating System macOS Sonoma 15.7.1 ### Browser (if applicable) Firefox ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When I run code in a python code block, I expect that it will run in pyodide. This was working in older versions of Open-Webui and is once again working, but was not working until I flushed my browser cache on one of my computers. This bug happened on Firefox for MacOS but not Firefox for Windows, although that may not have been the deciding factor. My windows device was also accessing the Docker image directly via local port, while the MacOS computer was accessing via Cloudflare tunnel, although again not sure if that's relevant. ### Actual Behavior Pyodide on my Mac machine was giving me an "Execution Time Exceeded" message in the status message under the code block. All other Webui features were working fine I decided to open up the browser log and saw ``` Lock file ABI version doesn't match Pyodide ABI version. lockfile version: 2024_0 pyodide version: 2025_0 ``` After I cleared all local site data AND closed openwebui on my Mac device I was able to get my computer to load a fully new version of pyodide and I could run in my browser. ### Steps to Reproduce It's a little unclear exactly what caused it. In my mind there are three options. 1. Firefox for Mac didn't ask correctly for the new version of Pyodide's lockfile, but Firefox for Windows did. 2. There were some strange cache setting related to the Cloudflare Tunnel setup that made some things not cache correctly. 3. Updating the UI on the server side WHILE having the UI open on my mac computer somehow meant it didn't ask for all up-to-date files. I'm using the most current version of Firefox - 144.0 on my Mac. ### Logs & Screenshots Relevant browser logs are: ``` Lock file ABI version doesn't match Pyodide ABI version. lockfile version: 2024_0 pyodide version: 2025_0 ``` ### Additional Information Mostly leaving this here to help other people troubleshoot in case they run into the same problem (I couldn't find an open issue mentioning pyodide in the repo). I also did a google search with my browser log snippet and came up with NOTHING even mildly related so I imagine some people would have a lot of trouble fixing this on their own. My suggested fixes would be one of the following: 1. More descriptive error message on pyodide failure. Instead of saying "Execution Time Exceeded" when pyodide doesn't even load say "Pyodide error - Check Browser Console" or something of that sort. 2. Have the UI detect Pyodide lockfile version mismatch and force the browser to reload. 3. On pyodide failure of any kind, try a full flush and reload of pyodide and all associated files (but max once per 30 minutes or something) I suspect that the true problem with Pyodide/WASM and caching is a result of them being newer technology (and me using the least supportive browser - Mac Firefox), so I imagine that fix 1 is the only reasonable one to maybe implement.

GiteaMirror added the bug label 2026-04-20 00:51:38 -05:00

GiteaMirror closed this issue

2026-04-20 00:51:39 -05:00

GiteaMirror referenced this issue

2026-04-20 05:37:38 -05:00

[PR #18649] [CLOSED] fix/image-in-collection #24867

GiteaMirror referenced this issue

2026-04-25 12:58:43 -05:00

[PR #18649] [CLOSED] fix/image-in-collection #40497

GiteaMirror referenced this issue

2026-04-29 23:22:08 -05:00

[PR #18649] [CLOSED] fix/image-in-collection #47915