[GH-ISSUE #17786] issue: LDAP connections are not closed #73002

Closed
opened 2026-05-13 05:15:59 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @NegaScout on GitHub (Sep 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17786

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

72e6959c7614

Ollama Version (if applicable)

No response

Operating System

Debian 12

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

LDAP route closes connections after auth or reuses them

Actual Behavior

LDAP route exists and leaks connections without ever sending close message to ldap, leading to "Bad Ber Tag or uncleanly closed connection"

Steps to Reproduce

  1. Start with clean install
  2. configure ldap
  3. perform any login action (does not have to be successfull)

Logs & Screenshots

{ "date": "[26\/Sep\/2025:14:11:29.527853602 +0000] ", "utc_time": "1758895889.527853602", "event": "BIND_SUCCESS", "dn": "xxx", "bind_method": "SIMPLE", "root_dn": false, "client_ip": "xxx", "server_ip": "xxx", "ldap_version": 3, "conn_id": xxx, "op_id": 0, "msg": "" }
{ "date": "[26\/Sep\/2025:14:11:38.140165961 +0000] ", "utc_time": "1758895898.140165961", "event": "TCP_ERROR", "client_ip": "xxx", "server_ip": "xxx", "ldap_version": 3, "conn_id": xxx, "msg": "Bad Ber Tag or uncleanly closed connection - B1" }

Additional Information

No response

Originally created by @NegaScout on GitHub (Sep 26, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17786 ### 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 72e6959c7614 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### 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 LDAP route closes connections after auth or reuses them ### Actual Behavior LDAP route exists and leaks connections without ever sending close message to ldap, leading to "Bad Ber Tag or uncleanly closed connection" ### Steps to Reproduce 1. Start with clean install 2. configure ldap 3. perform any login action (does not have to be successfull) ### Logs & Screenshots ``` { "date": "[26\/Sep\/2025:14:11:29.527853602 +0000] ", "utc_time": "1758895889.527853602", "event": "BIND_SUCCESS", "dn": "xxx", "bind_method": "SIMPLE", "root_dn": false, "client_ip": "xxx", "server_ip": "xxx", "ldap_version": 3, "conn_id": xxx, "op_id": 0, "msg": "" } { "date": "[26\/Sep\/2025:14:11:38.140165961 +0000] ", "utc_time": "1758895898.140165961", "event": "TCP_ERROR", "client_ip": "xxx", "server_ip": "xxx", "ldap_version": 3, "conn_id": xxx, "msg": "Bad Ber Tag or uncleanly closed connection - B1" } ``` ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-13 05:15:59 -05:00
Author
Owner

@tjbck commented on GitHub (Sep 28, 2025):

PR Welcome!

<!-- gh-comment-id:3343876821 --> @tjbck commented on GitHub (Sep 28, 2025): PR Welcome!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#73002