[GH-ISSUE #546] Persistent OpenAI Key for Continued Access to ChatGPT Models #50781

New Issue

GiteaMirror · 2026-05-05T11:10:20-05:00

GiteaMirror commented

2026-05-05 11:10:20 -05:00

Originally created by @Grepta on GitHub (Jan 23, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/546

Is your feature request related to a problem? Please describe.
When restarting Ollama Web UI, any Open AI API key added in settings is cleared. This means each time the an API key needs to be re-added to get access to ChatGPT models.

Describe the solution you'd like
The option for persistent storage of the API key.

Describe alternatives you've considered
I haven't found an alternative, I've just re-entered the key each time the Docker container is restarted.

Additional context
I'm running Ollama Web UI in a Docker container on Windows (WSL2).

Originally created by @Grepta on GitHub (Jan 23, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/546 **Is your feature request related to a problem? Please describe.** When restarting Ollama Web UI, any Open AI API key added in settings is cleared. This means each time the an API key needs to be re-added to get access to ChatGPT models. **Describe the solution you'd like** The option for persistent storage of the API key. **Describe alternatives you've considered** I haven't found an alternative, I've just re-entered the key each time the Docker container is restarted. **Additional context** I'm running Ollama Web UI in a Docker container on Windows (WSL2).

GiteaMirror closed this issue

2026-05-05 11:10:21 -05:00

GiteaMirror commented

2026-05-05 11:10:24 -05:00

@justinh-rahb commented on GitHub (Jan 23, 2024):

You can set a container environment variable by adding -e OPENAI_API_KEY=your_api_key to your docker run command, or adding another line to the environment section of the ollama-webui service in your Docker Compose file, depending how you launched it.

@justinh-rahb commented on GitHub (Jan 23, 2024): You can set a container environment variable by adding `-e OPENAI_API_KEY=your_api_key` to your `docker run` command, or adding another line to the environment section of the ollama-webui service in your Docker Compose file, depending how you launched it.

GiteaMirror commented

2026-05-05 11:10:27 -05:00

@mtompkins commented on GitHub (Jan 25, 2024):

It may be worth considering moving the OpenAI implementation / API key to the user level as this bears a cost. That way the server "owner" wouldn't have to worry about users and their usage on the paid API.

@mtompkins commented on GitHub (Jan 25, 2024): It may be worth considering moving the OpenAI implementation / API key to the user level as this bears a cost. That way the server "owner" wouldn't have to worry about users and their usage on the paid API.

GiteaMirror commented

2026-05-05 11:10:31 -05:00

@justinh-rahb commented on GitHub (Jan 25, 2024):

It may be worth considering moving the OpenAI implementation / API key to the user level as this bears a cost. That way the server "owner" wouldn't have to worry about users and their usage on the paid API.

@mtompkins This was the previous implementation, it was moved from client-side to backend in #381

@justinh-rahb commented on GitHub (Jan 25, 2024): > It may be worth considering moving the OpenAI implementation / API key to the user level as this bears a cost. That way the server "owner" wouldn't have to worry about users and their usage on the paid API. @mtompkins This was the previous implementation, it was moved from client-side to backend in #381

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#50781