From a77797ed1249da68967e06b44ae3a6ef17afaa88 Mon Sep 17 00:00:00 2001 From: ai-bot Date: Thu, 24 Sep 2026 15:50:46 +0000 Subject: [PATCH] Document the Open WebUI connection steps for end users --- instructions.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/instructions.md b/instructions.md index 6afbf8c..4c30e3c 100644 --- a/instructions.md +++ b/instructions.md @@ -65,6 +65,22 @@ Page shows the same list. Requests are billed to your saved API key by default. To bill a different PPQ.AI key per request, pass it as an `Authorization: Bearer` header. +### Open WebUI (or any service on this same server) + +Open WebUI and this proxy are separate StartOS services. From one container to +another, the LAN `https://` address fails certificate validation — the calling +container does not trust this server's self-signed Root CA. Use the internal +LXC-bridge address instead, which is plain HTTP (no TLS involved): + +1. On this service, run the **Service-to-Service URL** action (Actions tab). +2. Copy the URL it prints — `http://:/v1`. +3. In Open WebUI: **Admin Panel → Connections → OpenAI API**, paste the URL in + the URL field, click **Save**, and add the `private/` model IDs shown on the + Status Page (for example `private/glm-5-2`). + +Any other service container on the same server can use the same URL. It is not +reachable from your browser — that is what the LAN `https://` address is for. + ### Replacing the key Either surface works, and both write the same place: **Replace key** on the @@ -82,4 +98,4 @@ address, it means anyone with the address. Keeping it on the LAN, or on Tor with the address kept private, is the safe default. Backups of this service include your saved API key, and restoring a backup -restores it — keep that in mind when handling backup drives. +restores it — keep that in mind when handling backup drives. \ No newline at end of file