[GH-ISSUE #21300] issue: LDAP authentication causes the service to hang #19435

Closed
opened 2026-04-20 01:53:39 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @Booting-O on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21300

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.7.2

Ollama Version (if applicable)

0.15.2

Operating System

RedHat 9.4

Browser (if applicable)

Chrome 129

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

When I enable LDAP authentication, if I enter an incorrect account, it prompts me that the account does not exist.

Actual Behavior

In fact, when I enter an incorrect account, it causes the entire service to freeze, and I have to restart the container to recover.

Steps to Reproduce

  1. Enable LDAP
  2. Log in with a non-existent account
  3. The entire service will freeze

Logs & Screenshots

non

Additional Information

No response

Originally created by @Booting-O on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21300 ### 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 have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.7.2 ### Ollama Version (if applicable) 0.15.2 ### Operating System RedHat 9.4 ### Browser (if applicable) Chrome 129 ### 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 When I enable LDAP authentication, if I enter an incorrect account, it prompts me that the account does not exist. ### Actual Behavior In fact, when I enter an incorrect account, it causes the entire service to freeze, and I have to restart the container to recover. ### Steps to Reproduce 1. Enable LDAP 2. Log in with a non-existent account 3. The entire service will freeze ### Logs & Screenshots non ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 01:53:39 -05:00
Author
Owner

@tjbck commented on GitHub (Feb 12, 2026):

Should be addressed with a4281f6a7f in dev.

<!-- gh-comment-id:3887966574 --> @tjbck commented on GitHub (Feb 12, 2026): Should be addressed with a4281f6a7fbc9764b57830e4ef81bb780aa34af9 in dev.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#19435