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.   

 

 

 

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 January 5, 20215 yr by jbquintal
added pictures

11 minutes ago, jbquintal said:

tried some of the solutions

like what?

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

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

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?

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

 

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! 

I rebooted the server as soon as my parity check finished.  I'm able to access the WebGUI now.  I'll update this post if it acts up again.

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/

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.

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. 

 

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 February 11, 20242 yr by sMACk
progress

On 2/11/2024 at 1:38 PM, sMACk said:

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

Was this the culprit? My Unraid running 6.12.10, I can ssh and access other dockers, but not the webgui.

On 7/31/2024 at 10:38 PM, Waddoo said:

Was this the culprit? My Unraid running 6.12.10, I can ssh and access other dockers, but not the webgui.

I believe it was, apologies for taking so long to respond!

I am having similar issues and just removed the GPUstatistics plugin. Lets see if this solve my problem

@SimonF Here, are you aware of such issue ?

One potential cause of a 500 error when logging in was fixed in 6.12.11.  If you are on an earlier release try this from the console or SSH:
 

rm /var/log/pwfail/*

 

If that solves the problem, then if it happens again another short term workaround is to login to the webGUI from a different IP address.  But really your best bet is to upgrade to the latest stable release.

My service programs are running normally, but I cannot log in via SSH because I do not have this permission. Is there any other way to solve this problem?

21 minutes ago, Myptyun said:

but I cannot log in via SSH because I do not have this permission.

Has SSH access been enabled under Settings->Management Access?

11 hours ago, itimpi said:

Has SSH access been enabled under Settings->Management Access?
是否在“设置”->“管理访问”下启用了 SSH 访问？

I didn't enable this, but after a few hours, I found that it was normal. But what should I pay attention to? Do I need to keep SSH enabled for a long time in the future?

On 12/5/2024 at 3:00 AM, ljm42 said:

One potential cause of a 500 error when logging in was fixed in 6.12.11.  If you are on an earlier release try this from the console or SSH:
登录时出现 500 错误的一个潜在原因已在 6.12.11 中修复。如果您使用的是早期版本，请从控制台或 SSH 尝试以下作：
 

rm /var/log/pwfail/*

 

If that solves the problem, then if it happens again another short term workaround is to login to the webGUI from a different IP address.  But really your best bet is to upgrade to the latest stable release.
如果这解决了问题，那么如果它再次发生，另一个短期解决方法是从不同的 IP 地址登录到 webGUI。 但实际上，最好的选择是升级到最新的稳定版本。

I used your command and it returned the result rm: cannot remove '/var/log/pwfail/*': No such file or directory

/etc/rc.d/rc.php-fpm restart just brought back my gui. However I think there is an issue with pre-clear and the dashboard. As soon as I try the dashboard tab the GUI crashes again.