github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #19496] issue: 500 internal server error appears in v0.6.40 #18902

New Issue
Closed
opened 2026-04-20 01:10:40 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 01:10:40 -05:00
Owner
Copy Link

Originally created by @cloudtuotuo on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19496

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.6.40

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

Everythin works fine.

Actual Behavior

I'm using Nginx Proxy Manager as a reverse proxy for Openwebui. After upgrading to v0.6.40, I encountered a 500 Internal Server Error when trying to access the New Chat feature. However, accessing the chat history worked fine. I downgraded to v0.6.38, and everything is functioning correctly again.

Steps to Reproduce

Upgrade to v0.6.40.

Logs & Screenshots

500 internal server error

Additional Information

No response

Originally created by @cloudtuotuo on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19496 ### 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.6.40 ### 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 Everythin works fine. ### Actual Behavior I'm using Nginx Proxy Manager as a reverse proxy for Openwebui. After upgrading to v0.6.40, I encountered a 500 Internal Server Error when trying to access the New Chat feature. However, accessing the chat history worked fine. I downgraded to v0.6.38, and everything is functioning correctly again. ### Steps to Reproduce Upgrade to v0.6.40. ### Logs & Screenshots 500 internal server error ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 01:10:40 -05:00
GiteaMirror commented 2026-04-20 01:10:42 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Nov 26, 2025):

Not able to reproduce. The issue likely stems from your Nginx Proxy Manager configuration for Open WebUI.

<!-- gh-comment-id:3579191351 --> @silentoplayz commented on GitHub (Nov 26, 2025): Not able to reproduce. The issue likely stems from your Nginx Proxy Manager configuration for Open WebUI.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#18902
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?