Using Lingxi AI Plaza in Open WebUI

Open WebUI (formerly Ollama WebUI) is an open-source AI client that supports multi-user, knowledge base, RAG, and private deployment. It supports custom OpenAI-compatible endpoints, allowing integration with Lingxi AI Plaza. This article describes the configuration process.

Application Process

To integrate Lingxi AI Plaza into Open WebUI, first go to the Lingxi AI Plaza Console to obtain your API Token for backup.

Get Lingxi AI Plaza API Key

If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in. After logging in or registering, you will be automatically returned to the current page.

During the first application, there will be a free quota provided to experience Lingxi AI Plaza's model services for free.

Deploying and Configuring Lingxi AI Plaza

Open WebUI connects to OpenAI-compatible endpoints through environment variables, and can be deployed with a single Docker command (replace {token} with your Token):

docker run -d \
  --name open-webui \
  -p 3000:8080 \
  -e WEBUI_SECRET_KEY=$(openssl rand -base64 32) \
  -e OPENAI_API_BASE_URL=https://api.acedata.cloud/v1 \
  -e OPENAI_API_KEY={token} \
  -v open-webui:/app/backend/data \
  ghcr.io/open-webui/open-webui:main
Environment Variable Function
OPENAI_API_BASE_URL Lingxi AI Plaza entry, must end with /v1
OPENAI_API_KEY Your Token
WEBUI_SECRET_KEY Session encryption key, automatically generated
-v open-webui:/app/backend/data Persistent conversation / user data

Open http://your-server-IP:3000, and the first registered account will automatically become the administrator. Note the path rules for Base URL:

OPENAI_API_BASE_URL Actual Request Result
https://api.acedata.cloud/v1 https://api.acedata.cloud/v1/chat/completions Correct
https://api.acedata.cloud/openai https://api.acedata.cloud/openai/chat/completions Also available
https://api.acedata.cloud/openai/v1 https://api.acedata.cloud/openai/v1/chat/completions 404 (/openai does not have /v1)

After logging in, go to Admin Panel → Settings → Connections and click "Verify Connection" to validate; in Settings → Models, you can filter and pin commonly used models.

In addition to using environment variables, Open WebUI also supports adding connections directly in the interface: go to Admin Settings → Connections, click ➕ and fill in the URL (https://api.acedata.cloud/v1) and API Key, and Open WebUI will automatically call /models to fetch the model list. See the official documentation Starting With OpenAI-Compatible Servers.

Selecting Models

The model directory will continue to be updated. Prefer using the model list automatically loaded by the client; if manual entry is required, first request GET https://api.acedata.cloud/v1/models to get the current model ID, then choose based on the context, image, and tool invocation capabilities supported by the client.

Verifying Integration

If you are unsure whether the issue lies with Open WebUI or the network, you can first verify the endpoint directly using curl (replace {token} with your Token):

curl -X POST 'https://api.acedata.cloud/v1/chat/completions' \
  -H 'Authorization: Bearer {token}' \
  -H 'Content-Type: application/json' \
  -d '{
    "model": "MODEL_ID",
    "messages": [{"role": "user", "content": "ping"}]
  }'

Returning an OpenAI-compatible chat.completion object indicates that both the Token and endpoint are ready; if it returns HTTP 403 used_up, it means the Token is valid but the balance is insufficient, and you can recharge at the console.

Advanced: Knowledge Base and Multi-User

Open WebUI's knowledge base (RAG) uses ChromaDB by default to store vectors, and the embedding model can specify text-embedding-3-large (via Lingxi AI Plaza). The original document text only exists on your server, and only the matched segments will be sent to the model. In Admin Panel → Users, you can manage user roles (Pending / User / Admin); it is recommended to set the "Default User Role" to pending, requiring new users to be reviewed before they can use it, to prevent unauthorized registrations from consuming quotas. If using nginx as a reverse proxy, please add proxy_buffering off; and client_max_body_size 100M;.

Frequently Asked Questions

Prompt Connection error / 404

This is usually because OPENAI_API_BASE_URL is written as .../openai/v1 or is missing /v1. Change it to https://api.acedata.cloud/v1.

Unable to chat after uploading documents

In the RAG settings of the Admin Panel, set the embedding model to text-embedding-3-large (OpenAI provider).

Data loss after container restart

You need to mount the data volume at startup with -v open-webui:/app/backend/data.

Learn More