[GH-ISSUE #1197] How to properly configure SSE #3756

New issue

Closed

opened 2026-02-28 11:57:34 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 11:57:34 +03:00

Owner

Originally created by @alexanderdemidkin on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1197

I have a machine running Garuda Linux. I installed Nginx and Nginx-UI v2.1.9. In the Nginx-UI self-check, I see an error related to SSE. I configured Nginx according to the documentation: https://nginxui.com/guide/nginx-proxy-example , but the error persists.

Could you please advise how to properly configure SSE? Currently, I'm getting an error when viewing stub_status and a constant self-check warning about SSE.

I've attached the output of my Nginx config and the result of nginx -v / nginx -V.

nginx-ui.conf :

server {
    listen          80;
    listen          [::]:80;

    server_name     <my.domain.name>;
    return 301 https://$host$request_uri;
}

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    listen  443       ssl;
    listen  [::]:443  ssl;
    http2   on;

    server_name <my.domain.name>;
    
    ssl_certificate /etc/letsencrypt/live/<my.domain.name>/fullchain.pem;# managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/<my.domain.name>/privkey.pem;# managed by Certbot

    location / {
        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_http_version  1.1;
        proxy_set_header    Upgrade             $http_upgrade;
        proxy_set_header    Connection          $connection_upgrade;
        proxy_pass          http://127.0.0.1:9000/;
        proxy_set_header Upgrade '';
        proxy_set_header Connection '';
        proxy_cache off;
        proxy_buffering     off;
    }
}

nginx -V

nginx version: nginx/1.28.0
built with OpenSSL 3.5.0 8 Apr 2025
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/bin/nginx --modules-path=/usr/lib/nginx/modules --pid-path=/run/nginx.pid --lock-path=/run/lock/nginx.lock --user=http --group=http --http-log-path=/var/log/nginx/access.log --error-log-path=stderr --http-client-body-temp-path=/var/lib/nginx/client-body --http-proxy-temp-path=/var/lib/nginx/proxy --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-cc-opt='-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/build/nginx/src=/usr/src/debug/nginx -flto=auto' --with-ld-opt='-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto' --with-compat --with-debug --with-file-aio --with-http_addition_module --with-http_auth_request_module --with-http_dav_module --with-http_degradation_module --with-http_flv_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_mp4_module --with-http_perl_module=dynamic --with-http_random_index_module --with-http_realip_module --with-http_secure_link_module --with-http_slice_module --with-http_ssl_module --with-http_stub_status_module --with-http_sub_module --with-http_v2_module --with-http_v3_module --with-http_xslt_module=dynamic --with-mail=dynamic --with-mail_ssl_module --with-pcre-jit --with-stream=dynamic --with-stream_geoip_module=dynamic --with-stream_realip_module --with-stream_ssl_module --with-stream_ssl_preread_module --with-threads

Originally created by @alexanderdemidkin on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1197 I have a machine running Garuda Linux. I installed Nginx and Nginx-UI v2.1.9. In the Nginx-UI self-check, I see an error related to SSE. I configured Nginx according to the documentation: [https://nginxui.com/guide/nginx-proxy-example ](https://nginxui.com/guide/nginx-proxy-example), but the error persists. Could you please advise how to properly configure SSE? Currently, I'm getting an error when viewing stub_status and a constant self-check warning about SSE. I've attached the output of my Nginx config and the result of nginx -v / nginx -V. nginx-ui.conf : ``` server { listen 80; listen [::]:80; server_name <my.domain.name>; return 301 https://$host$request_uri; } map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 443 ssl; listen [::]:443 ssl; http2 on; server_name <my.domain.name>; ssl_certificate /etc/letsencrypt/live/<my.domain.name>/fullchain.pem;# managed by Certbot ssl_certificate_key /etc/letsencrypt/live/<my.domain.name>/privkey.pem;# managed by Certbot location / { 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_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_pass http://127.0.0.1:9000/; proxy_set_header Upgrade ''; proxy_set_header Connection ''; proxy_cache off; proxy_buffering off; } } ``` nginx -V ``` nginx version: nginx/1.28.0 built with OpenSSL 3.5.0 8 Apr 2025 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/bin/nginx --modules-path=/usr/lib/nginx/modules --pid-path=/run/nginx.pid --lock-path=/run/lock/nginx.lock --user=http --group=http --http-log-path=/var/log/nginx/access.log --error-log-path=stderr --http-client-body-temp-path=/var/lib/nginx/client-body --http-proxy-temp-path=/var/lib/nginx/proxy --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-cc-opt='-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/build/nginx/src=/usr/src/debug/nginx -flto=auto' --with-ld-opt='-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto' --with-compat --with-debug --with-file-aio --with-http_addition_module --with-http_auth_request_module --with-http_dav_module --with-http_degradation_module --with-http_flv_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_mp4_module --with-http_perl_module=dynamic --with-http_random_index_module --with-http_realip_module --with-http_secure_link_module --with-http_slice_module --with-http_ssl_module --with-http_stub_status_module --with-http_sub_module --with-http_v2_module --with-http_v3_module --with-http_xslt_module=dynamic --with-mail=dynamic --with-mail_ssl_module --with-pcre-jit --with-stream=dynamic --with-stream_geoip_module=dynamic --with-stream_realip_module --with-stream_ssl_module --with-stream_ssl_preread_module --with-threads ```

kerem closed this issue

2026-02-28 11:57:35 +03:00

kerem commented

2026-02-28 11:57:35 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 3, 2025):

We are currently considering re-structuring SSE back to WebSocket in order to enhance compatibility.

@0xJacky commented on GitHub (Jul 3, 2025): We are currently considering re-structuring SSE back to WebSocket in order to enhance compatibility.

kerem commented

2026-02-28 11:57:35 +03:00

Author

Owner

@alexanderdemidkin commented on GitHub (Jul 3, 2025):

Please tell me how I should proceed correctly for the application to work correctly. Do I need to use some other configuration now, or are there changes planned for future versions that will work with the configuration I provided.

@alexanderdemidkin commented on GitHub (Jul 3, 2025): Please tell me how I should proceed correctly for the application to work correctly. Do I need to use some other configuration now, or are there changes planned for future versions that will work with the configuration I provided.

kerem commented

2026-02-28 11:57:35 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 3, 2025):

Delete these two lines and wait for the release of v2.1.10. It might happen in just a few hours.

proxy_set_header Upgrade '';
proxy_set_header Connection '';

@0xJacky commented on GitHub (Jul 3, 2025): Delete these two lines and wait for the release of v2.1.10. It might happen in just a few hours. ``` proxy_set_header Upgrade ''; proxy_set_header Connection ''; ```