[GH-ISSUE #18461] issue: OpenWebUI on docker does not start due to global AWS outage #18603

Closed
opened 2026-04-20 00:49:13 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @nedjalko-milenkov on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18461

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

0.6.34

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04

Browser (if applicable)

No response

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

The web server should start and see a console message: "INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)"

Actual Behavior

The web server does not start and the latest message in the log is:

openWebUI-1 | INFO: Started server process [1]
openWebUI-1 | INFO: Waiting for application startup.
openWebUI-1 | 2025-10-20 13:24:17.287 | INFO | open_webui.utils.logger:start_logger:162 - GLOBAL_LOG_LEVEL: INFO
openWebUI-1 | 2025-10-20 13:24:17.287 | INFO | open_webui.main:lifespan:561 - Installing external dependencies of functions and tools...
openWebUI-1 | 2025-10-20 13:24:17.314 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:283 - No requirements found in frontmatter.

Steps to Reproduce

  1. On any linux distro install docker
  2. Create docker-compose.yml file with the following content:
services:
  openWebUI:
    image: ghcr.io/open-webui/open-webui:v0.6.34
    restart: always
    ports:
      - 8080:8080
  1. Run sudo docker compose up

You will not be able to start the web server.

Logs & Screenshots

openWebUI-2-1 | Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
openWebUI-2-1 | Loading WEBUI_SECRET_KEY from .webui_secret_key
openWebUI-2-1 | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
openWebUI-2-1 | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
openWebUI-2-1 | WARNI [open_webui.env]
openWebUI-2-1 |
openWebUI-2-1 | WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS.
openWebUI-2-1 |
openWebUI-2-1 | INFO [open_webui.env] VECTOR_DB: chroma
openWebUI-2-1 | INFO [open_webui.env] Embedding model set: sentence-transformers/all-MiniLM-L6-v2
openWebUI-2-1 | WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests.
openWebUI-2-1 |
openWebUI-2-1 | ██████╗ ██████╗ ███████╗███╗ ██╗ ██╗ ██╗███████╗██████╗ ██╗ ██╗██╗
openWebUI-2-1 | ██╔═══██╗██╔══██╗██╔════╝████╗ ██║ ██║ ██║██╔════╝██╔══██╗██║ ██║██║
openWebUI-2-1 | ██║ ██║██████╔╝█████╗ ██╔██╗ ██║ ██║ █╗ ██║█████╗ ██████╔╝██║ ██║██║
openWebUI-2-1 | ██║ ██║██╔═══╝ ██╔══╝ ██║╚██╗██║ ██║███╗██║██╔══╝ ██╔══██╗██║ ██║██║
openWebUI-2-1 | ╚██████╔╝██║ ███████╗██║ ╚████║ ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║
openWebUI-2-1 | ╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═══╝ ╚══╝╚══╝ ╚══════╝╚═════╝ ╚═════╝ ╚═╝
openWebUI-2-1 |
openWebUI-2-1 |
openWebUI-2-1 | v0.6.34 - building the best AI user interface.
openWebUI-2-1 |
openWebUI-2-1 | https://github.com/open-webui/open-webui
openWebUI-2-1 |
Fetching 30 files: 100%|██████████| 30/30 [00:00<00:00, 65061.59it/s]
openWebUI-2-1 | INFO: Started server process [1]
openWebUI-2-1 | INFO: Waiting for application startup.
openWebUI-2-1 | 2025-10-20 13:46:28.540 | INFO | open_webui.utils.logger:start_logger:162 - GLOBAL_LOG_LEVEL: INFO
openWebUI-2-1 | 2025-10-20 13:46:28.540 | INFO | open_webui.main:lifespan:561 - Installing external dependencies of functions and tools...
openWebUI-2-1 | 2025-10-20 13:46:28.554 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:283 - No requirements found in frontmatter.

Additional Information

Currently there is a global AWS outage and a lot of service are affected, however I am running OpenWebUI locally and it is not connected to any 3rd party services including AWS. Since today morning I cannot start the service. It is stuck on "Waiting for application startup.".

It seems OpenWebUI is making a web call to a 3rd party service that is currently unavailable and is blocking the whole application.

I thought the whole idea of OpenWebUI is to be self-hosted and independent of 3rd party services.

I have gone back to previous version and below version 0.5.16, the OpenWebUI works. After version 0.5.16 it stucks on "Waiting for application startup.". This means that there is a new feature that calls a 3rd party service that blocks the whole application.

Originally created by @nedjalko-milenkov on GitHub (Oct 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18461 ### 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 0.6.34 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04 ### Browser (if applicable) _No response_ ### 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 The web server should start and see a console message: "INFO: Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)" ### Actual Behavior The web server does not start and the latest message in the log is: openWebUI-1 | INFO: Started server process [1] openWebUI-1 | INFO: Waiting for application startup. openWebUI-1 | 2025-10-20 13:24:17.287 | INFO | open_webui.utils.logger:start_logger:162 - GLOBAL_LOG_LEVEL: INFO openWebUI-1 | 2025-10-20 13:24:17.287 | INFO | open_webui.main:lifespan:561 - Installing external dependencies of functions and tools... openWebUI-1 | 2025-10-20 13:24:17.314 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:283 - No requirements found in frontmatter. ### Steps to Reproduce 1. On any linux distro install docker 2. Create docker-compose.yml file with the following content: ``` services: openWebUI: image: ghcr.io/open-webui/open-webui:v0.6.34 restart: always ports: - 8080:8080 ``` 3. Run sudo docker compose up You will not be able to start the web server. ### Logs & Screenshots openWebUI-2-1 | Loading WEBUI_SECRET_KEY from file, not provided as an environment variable. openWebUI-2-1 | Loading WEBUI_SECRET_KEY from .webui_secret_key openWebUI-2-1 | INFO [alembic.runtime.migration] Context impl SQLiteImpl. openWebUI-2-1 | INFO [alembic.runtime.migration] Will assume non-transactional DDL. openWebUI-2-1 | WARNI [open_webui.env] openWebUI-2-1 | openWebUI-2-1 | WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS. openWebUI-2-1 | openWebUI-2-1 | INFO [open_webui.env] VECTOR_DB: chroma openWebUI-2-1 | INFO [open_webui.env] Embedding model set: sentence-transformers/all-MiniLM-L6-v2 openWebUI-2-1 | WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests. openWebUI-2-1 | openWebUI-2-1 | ██████╗ ██████╗ ███████╗███╗ ██╗ ██╗ ██╗███████╗██████╗ ██╗ ██╗██╗ openWebUI-2-1 | ██╔═══██╗██╔══██╗██╔════╝████╗ ██║ ██║ ██║██╔════╝██╔══██╗██║ ██║██║ openWebUI-2-1 | ██║ ██║██████╔╝█████╗ ██╔██╗ ██║ ██║ █╗ ██║█████╗ ██████╔╝██║ ██║██║ openWebUI-2-1 | ██║ ██║██╔═══╝ ██╔══╝ ██║╚██╗██║ ██║███╗██║██╔══╝ ██╔══██╗██║ ██║██║ openWebUI-2-1 | ╚██████╔╝██║ ███████╗██║ ╚████║ ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║ openWebUI-2-1 | ╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═══╝ ╚══╝╚══╝ ╚══════╝╚═════╝ ╚═════╝ ╚═╝ openWebUI-2-1 | openWebUI-2-1 | openWebUI-2-1 | v0.6.34 - building the best AI user interface. openWebUI-2-1 | openWebUI-2-1 | https://github.com/open-webui/open-webui openWebUI-2-1 | Fetching 30 files: 100%|██████████| 30/30 [00:00<00:00, 65061.59it/s] openWebUI-2-1 | INFO: Started server process [1] openWebUI-2-1 | INFO: Waiting for application startup. openWebUI-2-1 | 2025-10-20 13:46:28.540 | INFO | open_webui.utils.logger:start_logger:162 - GLOBAL_LOG_LEVEL: INFO openWebUI-2-1 | 2025-10-20 13:46:28.540 | INFO | open_webui.main:lifespan:561 - Installing external dependencies of functions and tools... openWebUI-2-1 | 2025-10-20 13:46:28.554 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:283 - No requirements found in frontmatter. ### Additional Information Currently there is a global AWS outage and a lot of service are affected, however I am running OpenWebUI locally and it is not connected to any 3rd party services including AWS. Since today morning I cannot start the service. It is stuck on "Waiting for application startup.". It seems OpenWebUI is making a web call to a 3rd party service that is currently unavailable and is blocking the whole application. I thought the whole idea of OpenWebUI is to be self-hosted and independent of 3rd party services. I have gone back to previous version and below version 0.5.16, the OpenWebUI works. After version 0.5.16 it stucks on "Waiting for application startup.". This means that there is a new feature that calls a 3rd party service that blocks the whole application.
GiteaMirror added the bug label 2026-04-20 00:49:13 -05:00
Author
Owner

@Classic298 commented on GitHub (Oct 20, 2025):

Cannot reproduce with provided steps to reproduce. Works fine for me

<!-- gh-comment-id:3422160482 --> @Classic298 commented on GitHub (Oct 20, 2025): Cannot reproduce with provided steps to reproduce. Works fine for me
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#18603