Description:
After updating to OpenWebUI v0.5.14, I encountered an issue where the API throws a Connection error: Object of type ModelModel is not JSON serializable. This appears when making requests to retrieve available models.
This issue affects the monitoring pipelines for the built-in OpenAI and Ollama models. Due to the error, their data is not being sent to the following monitoring pipelines:
Datadog
Langfuse
Installation Method
Git Clone
Docker
Environment
OpenWebUI Version: v0.5.14
Expected Behavior
The system should retrieve the model list without errors.
Actual Behavior
When calling get_all_models(), the system encounters a Connection error: Object of type ModelModel is not JSON serializable.
Steps to Reproduce
Install OpenWebUI v0.5.14.
Start the application and attempt to query models.
Observe the error in the logs.
Logs and Screenshots
INFO [open_webui.routers.openai] get_all_models()
Connection error: Object of type ModelModel is not JSON serializable
Connection error: Object of type ModelModel is not JSON serializable
Connection error: Object of type ModelModel is not JSON serializable
Additional Information
This issue was not present in the previous version (v0.5.12).
It seems related to a serialization issue in get_all_models().
Would appreciate any guidance on fixing this issue. Thanks! 🙏 @tjbck
cc: @maycszz
Originally created by @samuelpetermoshi on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10411
**Description:**
After updating to OpenWebUI v0.5.14, I encountered an issue where the API throws a `Connection error: Object of type ModelModel is not JSON serializable`. This appears when making requests to retrieve available models.
This issue affects the monitoring pipelines for the built-in OpenAI and Ollama models. Due to the error, their data is not being sent to the following monitoring pipelines:
1. Datadog
2. Langfuse
---
## **Installation Method**
- Git Clone
- Docker
## **Environment**
- **OpenWebUI Version:** v0.5.14
## **Expected Behavior**
The system should retrieve the model list without errors.
## **Actual Behavior**
When calling `get_all_models()`, the system encounters a `Connection error: Object of type ModelModel is not JSON serializable`.
## **Steps to Reproduce**
1. Install OpenWebUI v0.5.14.
2. Start the application and attempt to query models.
3. Observe the error in the logs.
## **Logs and Screenshots**
```log
INFO [open_webui.routers.openai] get_all_models()
Connection error: Object of type ModelModel is not JSON serializable
Connection error: Object of type ModelModel is not JSON serializable
Connection error: Object of type ModelModel is not JSON serializable
```
<img width="1277" alt="Image" src="https://github.com/user-attachments/assets/49022029-b064-4ac6-9bb9-bdcb2a2d6693" />
## **Additional Information**
- This issue was not present in the previous version (v0.5.12).
- It seems related to a serialization issue in `get_all_models()`.
Would appreciate any guidance on fixing this issue. Thanks! 🙏 @tjbck
cc: @maycszz
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 @samuelpetermoshi on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10411
Description:
After updating to OpenWebUI v0.5.14, I encountered an issue where the API throws a
Connection error: Object of type ModelModel is not JSON serializable. This appears when making requests to retrieve available models.This issue affects the monitoring pipelines for the built-in OpenAI and Ollama models. Due to the error, their data is not being sent to the following monitoring pipelines:
Installation Method
Environment
Expected Behavior
The system should retrieve the model list without errors.
Actual Behavior
When calling
get_all_models(), the system encounters aConnection error: Object of type ModelModel is not JSON serializable.Steps to Reproduce
Logs and Screenshots
Additional Information
get_all_models().Would appreciate any guidance on fixing this issue. Thanks! 🙏 @tjbck
cc: @maycszz
@tjbck commented on GitHub (Feb 20, 2025):
This might already be addressed in dev, testing wanted here!