Streaming output is not possible when using other nginx reverse proxy dify

[zj1451729260-commits]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

When using other nginx reverse proxy dify and calling /v1/chat-messages streaming output is not possible , my nginx config is:
server {
listen 8000;
server_name localhost;

location / {
    add_header X-Location "xunjian";
    set $loc "xunjian";
    proxy_buffering off;
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_read_timeout 1200s;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_pass http://192.168.10.15:8180;
}


location /dify/ {
    add_header X-Location "dify";
    set $loc "dify";
    proxy_buffering off;
    proxy_pass http://192.168.2.181/;

    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_read_timeout 1200s;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_cache off;
    proxy_set_header X-Accel-Buffering no;
    chunked_transfer_encoding on;
    gzip off;
    add_header X-Accel-Buffering no;
    add_header Cache-Control no-cache always;
}



location /gateway/ {
    proxy_buffering off;
    proxy_pass http://192.168.10.6:8080/gateway/;
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_read_timeout 1200s;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

location /files/ {
    alias /opt/files/;
    add_header Access-Control-Allow-Origin *;
    add_header Access-Control-Allow-Methods *;
    add_header Access-Control-Allow-Headers *;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP  $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

location /openai/ {
    proxy_buffering off;
    proxy_pass http://192.168.10.6:8082/;
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_read_timeout 1200s;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}



location ~ .*\.(php|py|asp|java|class|aspx)$ {  
    return 405;  
}

error_page 500 502 503 504 /50x.html;
location = /50x.html {
    root /usr/share/nginx/html;
}

location /markdown/ {
    alias /data/markdown/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP  $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

location /tqapp/ {
    alias /data/tqapp/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP  $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

location = /public/test/index.html {
    alias /data/test/index.html;
    default_type text/html;
}

location = /public/test {
    return 301 /public/test/index.html;
}

}

[dosubot[bot]]

Your nginx config for the /dify/ location looks mostly correct for SSE streaming, but there are a couple of things to check:

1. Dify already runs its own Nginx internally. When you proxy to http://192.168.2.181/, you're hitting Dify's built-in Nginx, which itself proxies to the API. That means you have two Nginx layers, and both must disable buffering for SSE to work [1]. Your outer proxy has proxy_buffering off, which is good — but make sure Dify's internal Nginx is also properly configured (it should be by default).

2. Missing Host header pass-through. Your /dify/ location does not set proxy_set_header Host $http_host; — it only sets X-Forwarded-Host. Dify's internal Nginx and API may behave differently without the correct Host header. Try adding:

proxy_set_header Host $http_host;

3. The Connection "upgrade" header may interfere with SSE. SSE uses regular HTTP/1.1 chunked responses, not WebSocket upgrades. Setting Connection "upgrade" unconditionally can confuse some proxy layers. Dify's own proxy config uses Connection "" for normal API routes and only sets Connection "upgrade" for the /socket.io/ WebSocket path [1]. Try changing to:

proxy_set_header Connection "";

4. Check for upstream buffering at 192.168.2.181. If there's yet another proxy or load balancer between your nginx and Dify's actual service, that layer also needs proxy_buffering off.

Recommended /dify/ block:

location /dify/ {
    proxy_pass http://192.168.2.181/;
    proxy_buffering off;
    proxy_cache off;
    proxy_http_version 1.1;
    proxy_set_header Host $http_host;
    proxy_set_header Connection "";
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-Host $host;
    proxy_read_timeout 3600s;
    proxy_send_timeout 3600s;
    chunked_transfer_encoding on;
    gzip off;
}

The key changes are: adding Host $http_host, switching Connection from "upgrade" to "", and increasing timeouts to match Dify's defaults of 3600s [1].

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.