Skip to main content
This page runs Open WebUI in one Docker container, points it at the gateway with two environment variables, and checks the path in order: the models list, a granted call, an ungranted call, then a chat in the browser. You need the token from Gateway access and Docker on the host.

Write the env file

Open WebUI reads its settings from the environment. Keep the token in a file that only you can read, and never put it on the command line. Create the env file without echoing the token. Paste the token at the prompt:
Replace <your-tenant-host> with your tenant host, for example app.example.com. The base URL ends in /api/llm/v1. Check that both keys are present, without printing the token:
Expected output:
openwebui.env holds a live token. Keep it out of version control and out of shared folders. Delete it when you remove the install.

Start the container

Create a named volume for Open WebUI’s data, then start the container from the pinned image. The volume keeps accounts, chats and settings across restarts and upgrades.
Expected output: a 64-character container ID, then the container shows health: starting for about a minute.
Wait until the status reads (healthy), then check the health endpoint:
Expected output:
If the health check stays at 000, the container has not finished starting. Read its log with docker logs open-webui.

Create the first admin

Open http://localhost:3000 in a browser. The first account you create becomes the admin. Enter a name, an email and a password in the sign-up form, then submit it.
Open WebUI sign-in page with Email and Password fields and a Sign in button

The sign-in page. The first account created on a new install becomes the admin.

Keep the admin password in your password manager. Open WebUI does not show it again.
After the first admin exists, turn off public sign-up. Add ENABLE_SIGNUP=false to openwebui.env, then recreate the container with docker rm -f open-webui and the same docker run command. The volume keeps the accounts.

Check the gateway path

Run the checks in order. Each one uses the same key the container uses, loaded from the env file. Load the env file into your shell for these checks only:

1. List the models

Expected output:
The list is the set of models the gateway serves to the tenant, and it can include models this token has no grant on. A listed model can still return 403, as step 3 shows. To see the IDs, run the same call without -o /dev/null. The granted model appears as azure-openai-main/o4-mini, with the provider prefix.

2. Call a granted model

Expected output:

3. Call a model without a grant

Expected output:
The response body names the account and the model, for example User openwebui-gw is not authorized to access model openai-main/gpt-4o-mini or model does not exist. A 403 here is the grant working. It is not an error in the install.

4. Call a bare model name

Expected output:
Use the provider-qualified ID in Open WebUI, not the bare name. Clear the variables when you are done:

Send the first chat

  1. Open http://localhost:3000 and sign in as the admin.
  2. Open a new chat.
  3. In the model picker at the top, choose azure-openai-main/o4-mini. If the model does not appear, check the grant in Gateway access.
  4. Send a short prompt, for example Reply with the word: ready.
The reply comes back from the provider through the gateway. If the chat returns an error, use the table in Troubleshoot.

Next steps