Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid UI not responding / eternal loading

Featured Replies

trying to access my Unraid Server via browser  (hostname.localtld / LAN IP/ Myservers LINK) results in eternal loading symbols.
I am assuming only the webinterface is affected, because dockers, ssh, shares all seem fine.
I tried restarting the nginx  with `/etc/rc.c/rc.nginx reload` but other than canceling the currently loading browser tabs to a "error 500" nothing changed.

When I checked the My Servers page, I noticed it said that the servers was not connected, so I restarted the unraid-api as well, which brought back the green light in My Servers, but otherwise did not change anything.

 

I tried to create a diagnostics file (via ssh), but the process also just continues running.   

I have tailed syslog for a bit, but all I'm seeing are errors like this:

Feb  4 17:34:35 <SERVERNAME> nginx: 2023/02/04 17:34:35 [error] 22319#22319: *1228637 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 2001:9e8:222d:af00:5cc6:dd32:XXXX:YYYY, server: , request: "GET /favicon.ico HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "<SERVERNAME>.<LOCALTLD>:<PORT>", referrer: "https://<SERVERNAME>.<LOCALTLD>:<PORT>/Apps"

Feb  4 17:34:35 <SERVERNAME> nginx: 2023/02/04 17:34:35 [error] 22319#22319: *1228637 auth request unexpected status: 504 while sending to client, client: 2001:9e8:222d:af00:5cc6:dd32:XXXX:YYYY, server: , request: "GET /favicon.ico HTTP/2.0", host: "<SERVERNAME>.<LOCALTLD>:<PORT>", referrer: "https://<SERVERNAME>.<LOCALTLD>:<PORT>/Apps

I'll also attach the syslog. 


It might be unrelated, but I've had the UI be unresponsive once before this week, when I used the Theme Engine. In a video tutorial I heard a warning about not submitting twice after loading from css input (too late), and this seemed to crash my UI as well. Weirdly enough when I tried to restart the UI (or rather nginx) ssh also became unresponsive so I reset my server. SSH is fine right now, so I am not sure these are related.

--- Edit:
I found another thing might've stopped working:
`nvidia-smi`, when I call this it also takes forever, so I suspect that the driver crashed or something?
I am not sure how this could relate to the webui though, I am sure I the only thing showing on the monitor was a CLI, not the UI (when I started the server, disconnected the monitor since)
---

syslog-anon.zip

Edited by wambo

  • Community Expert

Have you updated your cert?

 

  • Author

AFAIK already quite a while ago.  Not sure whether I can control that via CLI.  
Is there anything that hints you to believe I did not? Or is that just the first reaction to anything webui related?

But following that link showed me how to disabled ssl just to verify - this also shows the same behaviour (on a different port now of course)

--> So same behaviour on http.
So I am going to turn ssl back on. ..... After we can fix this issue. Why can I turn it off via CLI but not on ?

Edited by wambo

  • Author

I tried a the `powerdown -r` after getting a hint about gpustats plugin causing issues. 
But looks like this script did not fully go through. Shares are still accessible, ssh is unresponsive (although not getting refused or anything, just nothing happening after typing that command). I had to hardreset the system.

About the failed powerdown the guess (from discord) is that a service was hanging.

 

Still no further clue about the underlying issue. 

Edited by wambo

  • Community Expert

Try booting in safe mode, if still issues probably easiest to just redo the flash drive.

  • Author

This is not a permanently reoccurring error, and it doesn't seem to start after boot but a after quite some time of running, so I don't see any reason that justifies setting everything up again (or does "redo the flash drive" refer to copy&pasting to a new drive? - Seems even less likely to improve anything). "Just format and install again" is just so windows like, I really didn't expect to hear that 

Until now we've established that it does not affect many areas of the system. but does affect the UI of Unraid, not the nginx but it's "upstream"  - I was hoping someone could shed some light on what that would be, and whether I could test for its health next time it happens ( if it happens).


It's possibly that it was GPUstat or at least connected with my GPU (nvidia P400) because that is a rather new component, and I did not use it much previously. 

  • 2 weeks later...
  • Author

 For now it seems as if uninstalling GPUstat solved the issue. Has been running fine ever since.

 

--- Edit
Spoke to early (mabye?)
I noticed I couldn't stop a docker container, tried to stop the docker service, which did not start back up.
Trying to reboot failed and stopping the array is not coming to an end.
Might be related or might not be related...
 

Feb 21 20:37:10 <SERVER> nginx: 2023/02/21 20:37:10 [error] 22153#22153: *3456794 upstream timed out (110: Connection timed out) while reading response header from upstream, client: <client.ip>, server: , request: "POST /webGui/include/Boot.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "<serverip:sslport>", referrer: "https://<server:port>/Settings/DockerSettings"


Found another one in the syslog 😕 Although this is probably connected to docker not responding.

Edited by wambo

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.