Aerowinder

I do not.

No, I never found the solution. I just gave up. I got around it by doing this: Domain I wanted to go to Unraid: unraid.domain.com. Domain that now goes to Unraid: unraid.dev.domain.com. So basically my setup is as follows: DNS: unraid.domain.com = reverse proxy IP DNS: unraid.dev.domain.com = unraid box IP Reverse proxy: 301 redirect unraid.domain.com TO unraid.dev.domain.com Browsing to unraid.domain.com redirects to unraid.dev.domain.com, which points directly to Unraid.

Any chance of getting some buttons next to the date picker? Like: Last Hour Last 30 Minutes Last 5 Minutes, etc? It's kind of annoying to have to mess with the date picker every time i want to see what just woke a drive up. It seems like there's plenty of space for some buttons in that location.

Thank you for pasting these. Unfortunately, none of these helped with the issue. I'm running the proxy on AlmaLinux, which uses NGINX 1.20 by default. I made some changes with DNF and got it to install 1.26 where the issue yet persists. Pretty much at a loss as to why it does this. I even took a look at the NGINX config that Unraid is using, and I didn't see anything out of the ordinary.

Interesting. Could I get a look inside those conf files? Everything you pasted is pretty boilerplate.

Greetings, As the title says, Unraid behind an NGINX reverse proxy initially works, but will become unresponsive in ~30-45 seconds. * This problem may occur on older versions, I just started using Unraid again * I am using NGINX reverse proxy function * NGINX lives on a system that is external to Unraid, but internal to my network * Neither NGINX nor Unraid have exposure to the Internet * DNS resolution is happening internally, no external influence * The connection (unraid.domain.com) works fine - websockets enabled. But after 30-45 seconds or so, the websockets stop updating. The websocket stuff - graphs, drive rw - freezes in place * I use many websocket-based services behind this reverse proxy, Unraid is the only one with issues * Affects Firefox and Chrome * Affects Windows and Linux When this occurs, I can still navigate using the menu buttons. And when I do click one, everything works fine again for about 30-45 more seconds before the websockets die again. My NGINX reverse proxy configuration is as follows: server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name unraid.domain.com; include ./conf.d/domain.com.sslsettings; access_log /var/log/nginx/unraid-access.log; error_log /var/log/nginx/unraid-error.log; location / { proxy_pass https://192.168.10.40:443; 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 "upgrade"; proxy_read_timeout 300s; proxy_send_timeout 300s; proxy_connect_timeout 75s; proxy_buffering off; } } I did try disabling HTTPS, but this didn't change anything. I think the SSL errors are a red herring: unraid-error.log: 2025/06/18 20:50:14 [crit] 4090#4090: 1259 SSL_do_handshake() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while SSL handshaking, client: 192.168.10.10, server: 0.0.0.0:443 2025/06/18 20:50:14 [crit] 4089#4089: 1260 SSL_do_handshake() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while SSL handshaking, client: 192.168.10.10, server: 0.0.0.0:443 2025/06/18 22:04:22 [crit] 4089#4089: 3583 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while processing HTTP/2 connection, client: 192.168.10.10, server: 0.0.0.0:443 2025/06/18 22:04:38 [crit] 4090#4090: 3688 SSL_do_handshake() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while SSL handshaking, client: 192.168.10.10, server: 0.0.0.0:443 2025/06/18 22:05:11 [crit] 4090#4090: 3584 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while processing HTTP/2 connection, client: 192.168.10.10, server: 0.0.0.0:443 2025/06/18 22:05:16 [crit] 4090#4090: 3702 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while proxying upgraded connection, client: 192.168.10.10, server: unraid.domain.com, request: "GET /sub/cpuload,update1,update2,update3 HTTP/1.1", upstream: "https://192.168.10.40:443/sub/cpuload,update1,update2,update3", host: "unraid.domain.com" 2025/06/18 22:05:16 [crit] 4089#4089: 3695 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while proxying upgraded connection, client: 192.168.10.10, server: unraid.domain.com, request: "GET /sub/wlan0 HTTP/1.1", upstream: "https://192.168.10.40:443/sub/wlan0", host: "unraid.domain.com" 2025/06/18 22:05:16 [crit] 4090#4090: 3705 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while proxying upgraded connection, client: 192.168.10.10, server: unraid.domain.com, request: "GET /sub/session,var,notify HTTP/1.1", upstream: "https://192.168.10.40:443/sub/session,var,notify", host: "unraid.domain.com" 2025/06/18 22:05:16 [crit] 4090#4090: *3752 SSL_read() failed (SSL: error:0A000126:SSL routines::unexpected eof while reading) while processing HTTP/2 connection, client: 192.168.10.10, server: 0.0.0.0:443 Anyone running a similar setup that has working websockets?

Is this no longer working on the 6.4 betas? My modules are coretemp and jc42. Available sensors will sometimes show up in the drop down box (not usually), but when I attempt to save the selections, they revert back to Not used.