[GH-ISSUE #8374] Empty response when the deployment is behind a reverse proxy with HTTPS enabled #69705

New Issue

GiteaMirror · 2026-05-13T02:00:18-05:00

GiteaMirror commented

2026-05-13 02:00:18 -05:00

Originally created by @zx2015 on GitHub (Jan 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8374

Bug Report

I am experiencing an issue with OpenWebUI deployed behind a reverse proxy. While I can access the OpenWebUI page via HTTPS, submitting a question results in an empty response.
Refer to below picture

If I use HTTP, the Open WebUI works normally.

Installation Method

The Open WebUi is deployed with Docker.

Environment

Open WebUI Version: v0.5.4 (I also tried v0.5.0 ~ v0.5.3, same problem exists)
**Litellm[Proxy]: 1.56.9
Operating System: [e.g., Ubuntu 24.04 server, Windows 11 Client]
Browser (if applicable): [e.g., MS Edge 131.0.2903.112]

Nginx Configuration:

``
server {
listen 443 ssl default_server;
listen [::]:443 ssl default_server;

      root /var/www/html;
  
      ssl_certificate "/etc/nginx/ssl/server.crt";
      ssl_certificate_key "/etc/nginx/ssl/server.key";
      ssl_protocols TLSv1.2 TLSv1.3;
  
      ssl_session_cache shared:SSL:10m;
      ssl_session_timeout 1d;
      ssl_buffer_size 4k;
  
  
      server_name _;
  
      location / {
              proxy_pass http://localhost;
              proxy_set_header Host $host;
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              proxy_set_header X-Forwarded-Proto $scheme;
              proxy_buffering off;
      }
  }

``

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.

Originally created by @zx2015 on GitHub (Jan 7, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8374 # Bug Report I am experiencing an issue with OpenWebUI deployed behind a reverse proxy. While I can access the OpenWebUI page via HTTPS, submitting a question results in an empty response. Refer to below picture ![image](https://github.com/user-attachments/assets/0bbc200c-23d5-45a7-970f-7dfffd8d01f8) If I use HTTP, the Open WebUI works normally. --- ## Installation Method The Open WebUi is deployed with Docker. ## Environment - **Open WebUI Version:** v0.5.4 (I also tried v0.5.0 ~ v0.5.3, same problem exists) - **Litellm[Proxy]: 1.56.9 - **Operating System:** [e.g., Ubuntu 24.04 server, Windows 11 Client] - **Browser (if applicable):** [e.g., MS Edge 131.0.2903.112] ## Nginx Configuration: `` server { listen 443 ssl default_server; listen [::]:443 ssl default_server; root /var/www/html; ssl_certificate "/etc/nginx/ssl/server.crt"; ssl_certificate_key "/etc/nginx/ssl/server.key"; ssl_protocols TLSv1.2 TLSv1.3; ssl_session_cache shared:SSL:10m; ssl_session_timeout 1d; ssl_buffer_size 4k; server_name _; location / { proxy_pass http://localhost; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_buffering off; } } `` **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. - [ ] 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.

GiteaMirror closed this issue

2026-05-13 02:00:18 -05:00

GiteaMirror commented

2026-05-13 02:00:19 -05:00

@tjbck commented on GitHub (Jan 7, 2025):

#8074

@tjbck commented on GitHub (Jan 7, 2025): #8074

GiteaMirror commented

2026-05-13 02:00:20 -05:00

@zx2015 commented on GitHub (Jan 7, 2025):

@tjbck Thank you very much. Case solved

@zx2015 commented on GitHub (Jan 7, 2025): @tjbck Thank you very much. Case solved