issue: Missing admin runtime creation

Originally created by @pyautoml on GitHub (Sep 22, 2025). Originally assigned to: @tjbck on GitHub. ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.30 ### Ollama Version (if applicable) 0.11.10 ### Operating System Ubuntu 22.04 ### Browser (if applicable) Chrome 140.0.7339.128 ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior **Goal:** Dynamic admin account creation during Docker container runtime by passing credentials from local .env file to the OpenWebUI's internal database. **Context:** Running OpenWebUI inside a container and publishing it as a GUI interface, there is a time gap between making the resource online and time when I need to create first user manually, via providing email and password (the website is already online and other users can see the admin landing page). I tried many configurations and was not able to create admin (and add its credentials to locally created .db) account, blocking by this ranom user access to the admin dashboard. **Encryption issue** I was able to force OpenWebUI to accept my credentials on the runtime, but it occurs that the encryption is not matching later (I assume OpenWebUI uses different encryption method) and provided data do not allow me to log in as administrator. **Not secure workarounds** The only 2 ways I am aware of is either by blocking port, accessing the dashboard, create admin manually, and then reopening the port, or by creating database on a host machine (not on the server), and then manually mounting it as a volume when creating container on the server. ### Actual Behavior I have provide admin account credentials manually after the container is UP displaying admin dashboard to random internet users. ### Steps to Reproduce 1. Prepare OpenWebUi as a Docker container file (Dockerfile + docker-compose.yml). 2. Provide local credentials (e.g. .env). 3. Run custom stript trying to create OpenWebUI's database and force to store admins data. 4. Once container is UP and available via domain (as a website), try to log in with created credentials (<-- this is when the concept fails) ### Logs & Screenshots There are no logs or screens as credentials data is a sensitive information. ### Additional Information I have troubleshoot this for the last 3 days. The most successful step was forcing OpenWebUI container to wait until I load my admin credentials, but the credentials are encrypted in such way that later providing correct ones still results in a mismatch (I provide correct email and password, I have exactly the same in the .db, but the GUI displays message regarding login failure).

GiteaMirror commented

2025-11-11 16:56:02 -06:00

Owner

Originally created by @pyautoml on GitHub (Sep 22, 2025).

Originally assigned to: @tjbck on GitHub.

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.30

Ollama Version (if applicable)

0.11.10

Operating System

Ubuntu 22.04

Browser (if applicable)

Chrome 140.0.7339.128

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Goal:
Dynamic admin account creation during Docker container runtime by passing credentials from local .env file to the OpenWebUI's internal database.

Context:
Running OpenWebUI inside a container and publishing it as a GUI interface, there is a time gap between making the resource online and time when I need to create first user manually, via providing email and password (the website is already online and other users can see the admin landing page). I tried many configurations and was not able to create admin (and add its credentials to locally created .db) account, blocking by this ranom user access to the admin dashboard.

Encryption issue
I was able to force OpenWebUI to accept my credentials on the runtime, but it occurs that the encryption is not matching later (I assume OpenWebUI uses different encryption method) and provided data do not allow me to log in as administrator.

Not secure workarounds
The only 2 ways I am aware of is either by blocking port, accessing the dashboard, create admin manually, and then reopening the port, or by creating database on a host machine (not on the server), and then manually mounting it as a volume when creating container on the server.

Actual Behavior

I have provide admin account credentials manually after the container is UP displaying admin dashboard to random internet users.

Steps to Reproduce

Prepare OpenWebUi as a Docker container file (Dockerfile + docker-compose.yml).
Provide local credentials (e.g. .env).
Run custom stript trying to create OpenWebUI's database and force to store admins data.
Once container is UP and available via domain (as a website), try to log in with created credentials (<-- this is when the concept fails)

Logs & Screenshots

There are no logs or screens as credentials data is a sensitive information.

Additional Information

I have troubleshoot this for the last 3 days. The most successful step was forcing OpenWebUI container to wait until I load my admin credentials, but the credentials are encrypted in such way that later providing correct ones still results in a mismatch (I provide correct email and password, I have exactly the same in the .db, but the GUI displays message regarding login failure).