mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 06:03:26 -05:00
[GH-ISSUE #7059] Various internal endpoints not working on a fresh install of 0.4.0 #134314
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @samling on GitHub (Nov 20, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7059
Bug Report
Installation Method
Kubernetes
Environment
Open WebUI Version: v0.4.0
Operating System: Ubuntu 24 (host)
Browser (if applicable): Chrome 130.0.6723.119
Confirmation:
Expected Behavior:
Certain endpoints to function correctly:
Actual Behavior:
Client-side 404s hitting various internal open-webui API endpoints
Description
Bug Summary:
I was initially experiencing issues having upgraded an existing deployment, so I backed up everything and started fresh in an incognito tab to rule out migration and cache issues.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'api_key')The container logs show FastAPI errors:
index.ts:170 POST https://open-webui.(mydomain)/api/v1/models/id/anthropic/claude-2/update 404 (Not Found)Nothing extra in the container logs, just a 404 attempting to hit the endpoint.
Reproduction Details
Steps to Reproduce:
Install open-webui 0.4.0 with no existing data
Create an account
Navigate to settings > account > "create new secret key"; observe console errors
Add a model provider (maybe specific to litellm?)
Edit a model, change the visibility to public, save (successful)
Edit the same mode, change the visibility to private, save (unsuccessful)
Any help is appreciated. Thank you!
@tjbck commented on GitHub (Nov 20, 2024):
Fixed on dev!
@samling commented on GitHub (Nov 20, 2024):
Unfortunately creating an API key still seems to be broken:
The issue with saving models after the first update persists as well.
@tjbck commented on GitHub (Nov 20, 2024):
Should be fixed with the latest dev 😅
@samling commented on GitHub (Nov 20, 2024):
Appreciate the super quick fixes! Happy to keep trying them as they roll out. 😄
@tjbck commented on GitHub (Nov 20, 2024):
As for the other issue, the model id containing '/' is not supported. You might want to try deleting the model if possible!
@samling commented on GitHub (Nov 20, 2024):
Got it - did that change in this version? They were working properly in 0.3.x. It's a naming convention I use in litellm to quickly find models by provider. Saving does work at least once, but maybe that creates a record that then has issues on subsequent updates?
@samling commented on GitHub (Nov 20, 2024):
I can confirm creating an API key works and removing
/from the model name fixes the other issue. Still not sure if the latter is a regression, but it's a small ask to update my model names to avoid the issue. Many thanks!@tjbck commented on GitHub (Nov 20, 2024):
Updated the endpoints to allow
/in the id, but I'd strongly discourage using/in the id in general, as they can be used as a part of url path parameters. Everything should work as intended now I believe, 0.4.1 will be released shortly!@samling commented on GitHub (Nov 20, 2024):
Understood, I totally understand from an API ambiguity perspective. Thank you so much!
@JunweiDuan commented on GitHub (Nov 25, 2024):
Solved or not? I meet the same issue, urgent, urgent, urgent.