Originally created by @rcalv002 on GitHub (Sep 9, 2024).
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: [e.g., v0.3.21
Operating System: Linux
Browser (if applicable): Edge, Brave
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Expected successful login as in previous versions
Actual Behavior:
As of latest release, unable to login via reverse proxy (been using Nginx Proxy Manager for years) with https://hostname.com, which worked without issue before, and continues to work for my other home lab services. Accessing directly via http://dockerip:exposedport works fine. Have cleared cache, tried different browsers and from different vms
Description
Bug Summary:
Unable to login, i get 502 or 504 errors and socket errors.
Reproduction Details
Steps to Reproduce:
Pull latest release with tag :latest on docker.
Spin up brand new container with different volume.
Login via direct http and create okay.
Point nginx proxy manager at this new container.
Open private session on same pc or another vm and try to browse to the secured host name, sits on login screen.
Logs and Screenshots
Browser Console Logs:
Docker Container Logs:
Additional Information
Proxy configuration has not changed and maintains websocket support
Originally created by @rcalv002 on GitHub (Sep 9, 2024).
# Bug Report
## Installation Method
Docker
## Environment
- **Open WebUI Version:** [e.g., v0.3.21
- **Operating System:** Linux
- **Browser (if applicable):** Edge, Brave
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Expected successful login as in previous versions
## Actual Behavior:
As of latest release, unable to login via reverse proxy (been using Nginx Proxy Manager for years) with https://hostname.com, which worked without issue before, and continues to work for my other home lab services. Accessing directly via http://dockerip:exposedport works fine. Have cleared cache, tried different browsers and from different vms
## Description
**Bug Summary:**
Unable to login, i get 502 or 504 errors and socket errors.
## Reproduction Details
**Steps to Reproduce:**
Pull latest release with tag :latest on docker.
Spin up brand new container with different volume.
Login via direct http and create okay.
Point nginx proxy manager at this new container.
Open private session on same pc or another vm and try to browse to the secured host name, sits on login screen.
## Logs and Screenshots
**Browser Console Logs:**

**Docker Container Logs:**

## Additional Information
Proxy configuration has not changed and maintains websocket support
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rcalv002 on GitHub (Sep 9, 2024).
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: [e.g., v0.3.21
Operating System: Linux
Browser (if applicable): Edge, Brave
Confirmation:
Expected Behavior:
Expected successful login as in previous versions
Actual Behavior:
As of latest release, unable to login via reverse proxy (been using Nginx Proxy Manager for years) with https://hostname.com, which worked without issue before, and continues to work for my other home lab services. Accessing directly via http://dockerip:exposedport works fine. Have cleared cache, tried different browsers and from different vms
Description
Bug Summary:
Unable to login, i get 502 or 504 errors and socket errors.
Reproduction Details
Steps to Reproduce:
Pull latest release with tag :latest on docker.
Spin up brand new container with different volume.
Login via direct http and create okay.
Point nginx proxy manager at this new container.
Open private session on same pc or another vm and try to browse to the secured host name, sits on login screen.
Logs and Screenshots
Browser Console Logs:

Docker Container Logs:

Additional Information
Proxy configuration has not changed and maintains websocket support