WebGUI unresponsive - Getting 500 Internal Server Error


Recommended Posts

Hi Everyone, for some reason I can't seem to access the webGUI.  I took a look at a few threads with the same issue and tried some of the solutions, but nothing worked or isn't applicable.  I'm currently doing a pre-clear of two drives and a parity check.  I'm able to access the machine via SSH and things seem to be working... All docker apps seem to be working just fine and are reachable via their respective webGUIs.   

 

image.thumb.png.db0aea80fe93cdec6f439ca50285733a.png

 

image.png.8a28a065e9f1d5bbba7431b61545eef2.png

 

That being said, I've attached my diagnostics file to see if anyone can help figure out what's wrong. I'll keep it up until the parity check finishes and I'll do a reboot to see if that resolves the issue.  By the way, is "powerdown -r" the right way to gracefully shutdown?

  cosmos-diagnostics-20210106-0037.zip

Edited by jbquintal
added pictures
Link to comment
10 minutes ago, trurl said:

like what?

Apologies for not outlining what I've tried.  In any case, here's what I've looked at so far.
 

https://forums.unraid.net/topic/87876-500-internal-server-error-solved/ <--- Doesn't seem to apply. I don't have any VLANs or any load balancing set up...
https://forums.unraid.net/topic/70428-unraid-500-internal-server-error/ <--- Doesn't seem to apply. Plex and other Dockers seem to work just fine. I can play vides on Plex... 
https://forums.unraid.net/topic/86364-500-internal-server-error-nginx/ <--- Doesn't seem to apply. Different error codes in /var/log/nginx...
https://www.reddit.com/r/unRAID/comments/7ygav2/webgui_500_internal_server_error/ <--- Tried this...

Link to comment
2 minutes ago, trurl said:

There has been some back and forth between Unassigned Devices and Preclear development recently so maybe something to do with the preclears?

Thanks.  I did notice the Unassigned Devices error keep cropping up.  I did a quick search before and it just says that it's caused by having multiple browsers open.  In any case, i'll just finish the parity check and reboot the server and observe if it'll happen again.

"powerdown -r" is the proper way to do it, right?

Link to comment
8 minutes ago, jbquintal said:

"powerdown -r" is the proper way to do it, right?

I hadn't needed to do that recently so I checked the code:

root@unSERVER:~# which powerdown
/usr/local/sbin/powerdown
root@unSERVER:~# cat /usr/local/sbin/powerdown
#!/bin/bash
logger "/usr/local/sbin/powerdown has been deprecated"
if [[ "$1" == "-r" ]]; then
  /sbin/reboot
else
  /sbin/init 0
fi
root@unSERVER:~#

Looks like that would log that it was deprecated and then go ahead and do

reboot

instead

 

Link to comment
11 minutes ago, trurl said:

I hadn't needed to do that recently so I checked the code:


root@unSERVER:~# which powerdown
/usr/local/sbin/powerdown
root@unSERVER:~# cat /usr/local/sbin/powerdown
#!/bin/bash
logger "/usr/local/sbin/powerdown has been deprecated"
if [[ "$1" == "-r" ]]; then
  /sbin/reboot
else
  /sbin/init 0
fi
root@unSERVER:~#

Looks like that would log that it was deprecated and then go ahead and do


reboot

instead

 

Thanks! 

Link to comment
  • 1 year later...
  • 1 month later...
On 8/15/2022 at 1:28 PM, ZION said:

I'm not sure why this was so difficult to find or answer but here is how to correct the error without restating the machine.

From the console, log in to the terminal using the Root account. Once logged in type the following command:

/etc/rc.d/rc.php-fpm restart

Done. You can now log back in via WebUI.

Other useful Unraid commands can be found here:

https://selfhosters.net/commands/

I dealt with this exact issue today and your response fixed things perfectly. Thank you.

  • Thanks 1
Link to comment
  • 3 months later...
On 8/15/2022 at 4:28 PM, ZION said:

I'm not sure why this was so difficult to find or answer but here is how to correct the error without restating the machine.

From the console, log in to the terminal using the Root account. Once logged in type the following command:

/etc/rc.d/rc.php-fpm restart

Done. You can now log back in via WebUI.

Other useful Unraid commands can be found here:

https://selfhosters.net/commands/

I have the same error but this did not fix the issue. 

 

Link to comment
  • 1 year later...

I am running into this issue regularly... I was fiddling with CPU isolation and pinning recently but can't think of anything else I changed that could be responsisble... anyone figure anything permanent out?

 

update: remove GPUstatistics plugin as that was identified as a potential culprit by others, waiting to see if the issue is resolved...

Edited by sMACk
progress
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.