Bug Report

After reverse proxying with Nginx over HTTPS, the chat in Chrome browser fails and reports a JSON format error.

Description

After reverse proxying with Nginx over HTTPS, the chat in Chrome browser fails and reports a JSON format error.
but other brower is working normal。

Bug Summary:
[Provide a brief but clear summary of the bug]
After reverse proxying with Nginx over HTTPS, the chat in Chrome browser fails and reports a JSON format error.
but other brower is working normal。

Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
server {
listen 8444 ssl;
client_max_body_size 50M;
server_name us01.xiaoxiong.cloudns.asia;
ssl_certificate /etc/nginx/ssl/us01.xiaoxiong.cloudns.asia/us01.xiaoxiong.cloudns.asia.crt;
ssl_certificate_key /etc/nginx/ssl/us01.xiaoxiong.cloudns.asia/us01.xiaoxiong.cloudns.asia.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers HIGH:!aNULL:!MD5;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 86400;

}

}

Expected Behavior:
[Describe what you expected to happen.]
when we chat with openai key ， any brower shuld be working normal.

Actual Behavior:
[Describe what actually happened.]

chrome is failed , but firefox / safari is ok

Environment

• Open WebUI Version: [main]

• Operating System: [Windows 10, macOS Big Sur, Ubuntu 20.04]

• Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
  Chrome 版本 126.0.6478.62

Installation Method

docker
docker run -d -p 3000:8080 -e OPENAI_API_KEY=your_secret_key -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main

[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!