I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
0.6.21
Ollama Version (if applicable)
0.11.4
Operating System
macOS Sonoma, Ubuntu 25.04, Windows
Browser (if applicable)
Safari, MS Edge, Chrome
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
To have no vulnerabilities during the running of the command npm install
Actual Behavior
13 vulnerabilities (6 low, 7 moderate)
BUT TO FIX THE BUG I'VE A SOLUTION (BUT IF YOU WANT TO TEST IT OUT MORE DO IT, OBV)
I've upgraded the requirements in package.json and now my upgraded version is:
ADDICTIONALLY
To solve a bug that I've see during the launch ERROR: peewee.OperationalError: unable to open database file
I've edit the env.py file With this add in line 223
# Ensure data directory exists so SQLite can create/open the DB file
try:
DATA_DIR.mkdir(parents=True, exist_ok=True)
except Exception as e:
# Don't crash on import; downstream code will log a clearer DB error
log = logging.getLogger(__name__)
log.warning(f"Unable to create DATA_DIR '{DATA_DIR}': {e}")
So I hope that this feedback will be taken into consideration and possibly implemented in future versions of Open-WebUI.
Steps to Reproduce
Compile the code following the instructions
Logs & Screenshots
Additional Information
Thanks for the consideration and have a great day
Originally created by @Jeremy-Developer-Page on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16455
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
0.6.21
### Ollama Version (if applicable)
0.11.4
### Operating System
macOS Sonoma, Ubuntu 25.04, Windows
### Browser (if applicable)
Safari, MS Edge, Chrome
### 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
To have no vulnerabilities during the running of the command npm install
### Actual Behavior
13 vulnerabilities (6 low, 7 moderate)
BUT TO FIX THE BUG I'VE A SOLUTION (BUT IF YOU WANT TO TEST IT OUT MORE DO IT, OBV)
I've upgraded the requirements in package.json and now my upgraded version is:
```
"version": "0.6.21",
"private": true,
"scripts": {
"dev": "npm run pyodide:fetch && vite dev --host",
"dev:5050": "npm run pyodide:fetch && vite dev --port 5050",
"build": "npm run pyodide:fetch && vite build",
"build:watch": "npm run pyodide:fetch && vite build --watch",
"preview": "vite preview",
"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
"lint": "npm run lint:frontend ; npm run lint:types ; npm run lint:backend",
"lint:frontend": "eslint . --fix",
"lint:types": "npm run check",
"lint:backend": "pylint backend/",
"format": "prettier --plugin-search-dir --write \"**/*.{js,ts,svelte,css,md,html,json}\"",
"format:backend": "black . --exclude \".venv/|/venv/\"",
"i18n:parse": "i18next --config i18next-parser.config.ts && prettier --write \"src/lib/i18n/**/*.{js,json}\"",
"cy:open": "cypress open",
"test:frontend": "vitest --passWithNoTests",
"pyodide:fetch": "node scripts/prepare-pyodide.js"
},
"devDependencies": {
"@sveltejs/adapter-node": "^2.1.2",
"@sveltejs/adapter-static": "^3.0.9",
"@sveltejs/kit": "^2.27.3",
"@sveltejs/vite-plugin-svelte": "^3.1.2",
"@tailwindcss/container-queries": "^0.1.1",
"@tailwindcss/postcss": "^4.0.0",
"@tailwindcss/typography": "^0.5.13",
"@typescript-eslint/eslint-plugin": "^8.31.1",
"@typescript-eslint/parser": "^8.31.1",
"cypress": "^13.15.0",
"eslint": "^8.57.1",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-cypress": "^3.4.0",
"eslint-plugin-svelte": "^2.43.0",
"i18next-parser": "^9.0.1",
"postcss": "^8.4.31",
"prettier": "^3.3.3",
"prettier-plugin-svelte": "^3.2.6",
"sass-embedded": "^1.81.0",
"svelte": "^4.2.18",
"svelte-check": "^3.8.5",
"svelte-confetti": "^1.3.2",
"tailwindcss": "^4.0.0",
"tslib": "^2.4.1",
"typescript": "^5.5.4",
"vite": "^5.4.19",
"vite-plugin-static-copy": "^2.3.1",
"vitest": "^3.2.4"
},
"overrides": {
"cookie": "^0.7.0",
"esbuild": "^0.25.8"
},
"type": "module",
"dependencies": {
"@azure/msal-browser": "^4.5.0",
"@codemirror/lang-javascript": "^6.2.2",
"@codemirror/lang-python": "^6.1.6",
"@codemirror/language-data": "^6.5.1",
"@codemirror/theme-one-dark": "^6.1.2",
"@floating-ui/dom": "^1.7.2",
"@huggingface/transformers": "^3.0.0",
"@joplin/turndown-plugin-gfm": "^1.0.62",
"@mediapipe/tasks-vision": "^0.10.17",
"@pyscript/core": "^0.4.32",
"@sveltejs/svelte-virtual-list": "^3.0.1",
"@tiptap/core": "^3.0.7",
"@tiptap/extension-bubble-menu": "^3.0.7",
"@tiptap/extension-code-block-lowlight": "^3.0.7",
"@tiptap/extension-drag-handle": "^3.0.7",
"@tiptap/extension-file-handler": "^3.0.7",
"@tiptap/extension-floating-menu": "^3.0.7",
"@tiptap/extension-highlight": "^3.0.7",
"@tiptap/extension-image": "^3.0.7",
"@tiptap/extension-link": "^3.0.7",
"@tiptap/extension-list": "^3.0.7",
"@tiptap/extension-mention": "^3.0.9",
"@tiptap/extension-table": "^3.0.7",
"@tiptap/extension-typography": "^3.0.7",
"@tiptap/extension-youtube": "^3.0.7",
"@tiptap/extensions": "^3.0.7",
"@tiptap/pm": "^3.0.7",
"@tiptap/starter-kit": "^3.0.7",
"@xyflow/svelte": "^0.1.19",
"async": "^3.2.5",
"bits-ui": "^0.21.15",
"chart.js": "^4.5.0",
"codemirror": "^6.0.1",
"codemirror-lang-elixir": "^4.0.0",
"codemirror-lang-hcl": "^0.1.0",
"crc-32": "^1.2.2",
"dayjs": "^1.11.10",
"dompurify": "^3.2.5",
"eventsource-parser": "^1.1.2",
"file-saver": "^2.0.5",
"focus-trap": "^7.6.4",
"fuse.js": "^7.0.0",
"heic2any": "^0.0.4",
"highlight.js": "^11.9.0",
"html-entities": "^2.5.3",
"html2canvas-pro": "^1.5.11",
"i18next": "^23.10.0",
"i18next-browser-languagedetector": "^7.2.0",
"i18next-resources-to-backend": "^1.2.0",
"idb": "^7.1.1",
"js-sha256": "^0.10.1",
"jspdf": "^3.0.0",
"katex": "^0.16.22",
"kokoro-js": "^1.1.1",
"leaflet": "^1.9.4",
"lowlight": "^3.3.0",
"marked": "^9.1.0",
"mermaid": "^11.6.0",
"paneforge": "^0.0.6",
"panzoom": "^9.4.3",
"pdfjs-dist": "^5.3.93",
"prosemirror-collab": "^1.3.1",
"prosemirror-commands": "^1.6.0",
"prosemirror-example-setup": "^1.2.3",
"prosemirror-history": "^1.4.1",
"prosemirror-keymap": "^1.2.2",
"prosemirror-markdown": "^1.13.1",
"prosemirror-model": "^1.23.0",
"prosemirror-schema-basic": "^1.2.3",
"prosemirror-schema-list": "^1.5.1",
"prosemirror-state": "^1.4.3",
"prosemirror-tables": "^1.7.1",
"prosemirror-view": "^1.34.3",
"pyodide": "^0.27.3",
"socket.io-client": "^4.2.0",
"sortablejs": "^1.15.6",
"svelte-sonner": "^0.3.19",
"tippy.js": "^6.3.7",
"turndown": "^7.2.0",
"turndown-plugin-gfm": "^1.0.2",
"undici": "^7.3.0",
"uuid": "^9.0.1",
"y-prosemirror": "^1.3.7",
"yaml": "^2.7.1",
"yjs": "^13.6.27"
},
"engines": {
"node": ">=18.13.0 <=22.x.x",
"npm": ">=6.0.0"
}
}
```
ADDICTIONALLY
To solve a bug that I've see during the launch
`ERROR: peewee.OperationalError: unable to open database file
`
I've edit the env.py file With this add in line 223
```
# Ensure data directory exists so SQLite can create/open the DB file
try:
DATA_DIR.mkdir(parents=True, exist_ok=True)
except Exception as e:
# Don't crash on import; downstream code will log a clearer DB error
log = logging.getLogger(__name__)
log.warning(f"Unable to create DATA_DIR '{DATA_DIR}': {e}")
```
So I hope that this feedback will be taken into consideration and possibly implemented in future versions of Open-WebUI.
### Steps to Reproduce
Compile the code following the instructions
### Logs & Screenshots
<img width="415" height="184" alt="Image" src="https://github.com/user-attachments/assets/60671c8c-2d43-45de-a63f-15ae58fa60be" />
### Additional Information
Thanks for the consideration and have a great day
GiteaMirror
added the bug label 2026-05-18 02:42:39 -05:00
@Jeremy-Developer-Page commented on GitHub (Aug 10, 2025):
Yeah but the tag --force not solve this problems.
In any case, if you do not wish to accept the feedback, I am sorry but there is nothing I can do about it, so have a nice day. If, on the other hand, you decide to implement the changes I suggested above, I will be happy to have been of assistance.
<!-- gh-comment-id:3172873085 -->
@Jeremy-Developer-Page commented on GitHub (Aug 10, 2025):
Yeah but the tag --force not solve this problems.
In any case, if you do not wish to accept the feedback, I am sorry but there is nothing I can do about it, so have a nice day. If, on the other hand, you decide to implement the changes I suggested above, I will be happy to have been of assistance.
@traumschule this was a temporary issue which was mentioned in the changelogs during that time where some packages would create problems, but using --force from a clean install would fix it
<!-- gh-comment-id:3419613204 -->
@Classic298 commented on GitHub (Oct 19, 2025):
@traumschule this **was** a temporary issue which was mentioned in the changelogs during that time where some packages would create problems, but using --force from a clean install would fix it
ricardo@ricardo-PC:~/IAI/dev/branchs/dev-FEAT-impro_Folders_Notes_Chat_Collections$ npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tiptap/extension-bubble-menu@2.26.1
npm error Found: @tiptap/core@3.0.7
npm error node_modules/@tiptap/core
npm error @tiptap/core@"^3.0.7" from the root project
npm error peer @tiptap/core@"^3.0.7" from @tiptap/extension-blockquote@3.0.7
npm error node_modules/@tiptap/extension-blockquote
npm error @tiptap/extension-blockquote@"^3.0.7" from @tiptap/starter-kit@3.0.7
npm error node_modules/@tiptap/starter-kit
npm error @tiptap/starter-kit@"^3.0.7" from the root project
npm error 22 more (@tiptap/extension-bold, @tiptap/extension-code, ...)
npm error
npm error Could not resolve dependency:
npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error node_modules/@tiptap/extension-bubble-menu
npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Conflicting peer dependency: @tiptap/core@2.26.3
npm error node_modules/@tiptap/core
npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error node_modules/@tiptap/extension-bubble-menu
npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/ricardo/.npm/_logs/2025-10-19T12_15_42_595Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/ricardo/.npm/_logs/2025-10-19T12_15_42_595Z-debug-0.log
(I'm also have to add "y-protocols": "^1.0.6", & change for node 23 in package.json before build it...now i have a script to do it)
<!-- gh-comment-id:3419622349 -->
@rgaricano commented on GitHub (Oct 19, 2025):
yes, for solve this:
```
ricardo@ricardo-PC:~/IAI/dev/branchs/dev-FEAT-impro_Folders_Notes_Chat_Collections$ npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tiptap/extension-bubble-menu@2.26.1
npm error Found: @tiptap/core@3.0.7
npm error node_modules/@tiptap/core
npm error @tiptap/core@"^3.0.7" from the root project
npm error peer @tiptap/core@"^3.0.7" from @tiptap/extension-blockquote@3.0.7
npm error node_modules/@tiptap/extension-blockquote
npm error @tiptap/extension-blockquote@"^3.0.7" from @tiptap/starter-kit@3.0.7
npm error node_modules/@tiptap/starter-kit
npm error @tiptap/starter-kit@"^3.0.7" from the root project
npm error 22 more (@tiptap/extension-bold, @tiptap/extension-code, ...)
npm error
npm error Could not resolve dependency:
npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error node_modules/@tiptap/extension-bubble-menu
npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Conflicting peer dependency: @tiptap/core@2.26.3
npm error node_modules/@tiptap/core
npm error peer @tiptap/core@"^2.7.0" from @tiptap/extension-bubble-menu@2.26.1
npm error node_modules/@tiptap/extension-bubble-menu
npm error @tiptap/extension-bubble-menu@"^2.26.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/ricardo/.npm/_logs/2025-10-19T12_15_42_595Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/ricardo/.npm/_logs/2025-10-19T12_15_42_595Z-debug-0.log
```
(I'm also have to add `"y-protocols": "^1.0.6",` & change for node 23 in `package.json` before build it...now i have a script to do it)
Well, i hope you solved the underlying issue because --force is never a clean solution.
<!-- gh-comment-id:3419777511 -->
@traumschule commented on GitHub (Oct 19, 2025):
Well, i hope you solved the underlying issue because `--force` is never a clean solution.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Jeremy-Developer-Page on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16455
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.21
Ollama Version (if applicable)
0.11.4
Operating System
macOS Sonoma, Ubuntu 25.04, Windows
Browser (if applicable)
Safari, MS Edge, Chrome
Confirmation
README.md.Expected Behavior
To have no vulnerabilities during the running of the command npm install
Actual Behavior
13 vulnerabilities (6 low, 7 moderate)
BUT TO FIX THE BUG I'VE A SOLUTION (BUT IF YOU WANT TO TEST IT OUT MORE DO IT, OBV)
I've upgraded the requirements in package.json and now my upgraded version is:
ADDICTIONALLY
To solve a bug that I've see during the launch
ERROR: peewee.OperationalError: unable to open database fileI've edit the env.py file With this add in line 223
So I hope that this feedback will be taken into consideration and possibly implemented in future versions of Open-WebUI.
Steps to Reproduce
Compile the code following the instructions
Logs & Screenshots
Additional Information
Thanks for the consideration and have a great day
@tjbck commented on GitHub (Aug 10, 2025):
Please read the changelogs,
--forceis required for the time being.@Jeremy-Developer-Page commented on GitHub (Aug 10, 2025):
Yeah but the tag --force not solve this problems.
In any case, if you do not wish to accept the feedback, I am sorry but there is nothing I can do about it, so have a nice day. If, on the other hand, you decide to implement the changes I suggested above, I will be happy to have been of assistance.
@traumschule commented on GitHub (Oct 19, 2025):
To install from docs we need to read the changelogs?
@Classic298 commented on GitHub (Oct 19, 2025):
@traumschule this was a temporary issue which was mentioned in the changelogs during that time where some packages would create problems, but using --force from a clean install would fix it
@rgaricano commented on GitHub (Oct 19, 2025):
yes, for solve this:
(I'm also have to add
"y-protocols": "^1.0.6",& change for node 23 inpackage.jsonbefore build it...now i have a script to do it)@traumschule commented on GitHub (Oct 19, 2025):
Well, i hope you solved the underlying issue because
--forceis never a clean solution.