Fix final instances of OpenWeb UI to Open WebUI

This commit is contained in:
chrishart0 2025-02-17 14:34:16 -05:00
parent 5bdd30aadf
commit 1db80f9760

View File

@ -17,7 +17,7 @@ OpenWeb UI exposes a health check endpoint at `/health` that returns a 200 OK st
```bash
# No auth needed for this endpoint
curl https://your-openweb-instance/health
curl https://your-open-webuiinstance/health
```
### Using Uptime Kuma
@ -27,7 +27,7 @@ OpenWeb UI exposes a health check endpoint at `/health` that returns a 200 OK st
2. Set the following configuration:
- Monitor Type: HTTP(s)
- Name: Open WebUI
- URL: `http://your-openweb-instance:8080/health`
- URL: `http://your-open-webuiinstance:8080/health`
- Monitoring Interval: 60 seconds (or your preferred interval)
- Retry count: 3 (recommended)
@ -45,7 +45,7 @@ See [API documentation](https://docs.openwebui.com/getting-started/api-endpoints
```bash
# See steps below to get an API key
curl -H "Authorization: Bearer sk-adfadsflkhasdflkasdflkh" https://your-openweb-instance/api/models
curl -H "Authorization: Bearer sk-adfadsflkhasdflkasdflkh" https://your-open-webuiinstance/api/models
```
### Authentication Setup
@ -68,7 +68,7 @@ Note: If you don't see the option to generate API keys in your Settings > Accoun
1. Create a new monitor in Uptime Kuma:
- Monitor Type: HTTP(s) - JSON Query
- Name: Open WebUI Model Connectivity
- URL: `http://your-openweb-instance:8080/api/models`
- URL: `http://your-open-webuiinstance:8080/api/models`
- Method: GET
- Expected Status Code: 200
- JSON Query: `$count(data[*])>0`
@ -104,7 +104,7 @@ To verify that models can actually process requests, you can monitor the chat co
```bash
# Test model response
curl -X POST https://your-openweb-instance/api/chat/completions \
curl -X POST https://your-open-webuiinstance/api/chat/completions \
-H "Authorization: Bearer sk-adfadsflkhasdflkasdflkh" \
-H "Content-Type: application/json" \
-d '{