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.

(SOLVED) Web UI not starting, 500 errors.

Featured Replies

Yesterday I was transferring some files from an external hdd (in a usb 3.0 dock) to the array. 

I mounted the ext hdd via the unassigned devices plug-in.

 

I was performing a verbose rsync, and after about half the directory was transferred I/O errors popped up. 

 

The external drive had become unmounted. I remounted in unassigned devices, and restarted the rsync. 

 

Eventually I noticed the same errors again, but this time I could not remount the hdd.

 

Unlike the first involuntary unmount, I could no longer see unassigned devices settings in the web ui.

 

Eventually the entire web ui stopped working, and gave me 500 errors.

I could ssh to the server, and all my docker containers were still working.

I tried a few things- restarting nginx, etc, per suggestions in the forum, but nothing brought the web ui back.

 

FYI: I tried two web browsers from my laptop (brave and firefox.) Neither worked, nor did accessing from a tablet and phone (chrome and brave.)

 

So finally I ran "diagnostics," and rebooted from the cli

#reboot

 

After restart, I still get 500 errors attempting to access the web ui.

I can access via ssh, and the docker containers all work. (Though SMB does not for some reason.)

 

Here is what I expect is the significant portion of the diagnostics syslog: 

24 07:30:25 azathoth nginx: 2021/01/24 07:30:25 [error] 6855#6855: *13573 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 192.168.1.109, server: , request: "GET /Main HTTP/1.1", subrequest: "/auth_request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.181"
Jan 24 07:30:25 azathoth nginx: 2021/01/24 07:30:25 [error] 6855#6855: *13573 auth request unexpected status: 504 while
sending to client, client: 192.168.1.109, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.181"

 

I deleated /boot/config/ssl per some suggestion in this forum, and rebooted again, and I still have the same problem.

 

Any suggestions? I am medium-level tech savvy fwiw.

azathoth-diagnostics-20210124-0757.zip

  • Community Expert

Try booting in safe mode and post diags after that if it still doesn't work.

  • Author

How do I boot in safe mode from the command line?

 

  • Community Expert

Edit syslinux.cfg on the flash drive and move "menu default" form normal to safe mode.

  • Community Expert

No, move it to the safe mode entry:

 

image.png.bdce661207d51d98b62284d1e7841546.png

  • Author

Took a minute to figure out, for future reference:

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label Unraid OS
  kernel /bzimage
  append initrd=/bzroot
label Unraid OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label Unraid OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Unraid OS GUI Safe Mode (no plugins)
  menu default
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

 

  • Author

I'll try the non GUI mode next if GUI safe mode gets me nowhere...
Thanks

  • Author

Here's the diagnostics file from GUI safe mode. Let me know if regular old safe mode is required.

I see no GUI, web or hdmi fwiw.

azathoth-diagnostics-20210125-0559.zip

  • Community Expert

Those diagas are not after booting in safe mode, probably the previous ones.

  • Author

I deleted the old archive before running diagnostics, the one I posted was the only diagnostics archive present. 

I'll reboot in non-GUI safe mode and give it another shot. Thanks for your help and patience, Jorge.

  • Author

reboot kicked my out of the terminal, but didn't reboot the system...
 

root@azathoth:~# uptime -s
2021-01-23 10:26:07

Gonna try shutdown instead of reboot. 

wish me luck :)

  • Author

I shutdown dockerd, unmounted all the disks, and reboot and shutdown still do nothing other than boot me from a terminal. I'm going to pull power and rebuild the usb drive. This is taking too much time. 

 

  • Author

Hard reboot gave me access to web ui. Considering this solved, will start new thread of I encounter unsurmountable problems. Thanks Jorge.

azathoth-diagnostics-20210125-1043.zip

Edited by naught

  • naught changed the title to (SOLVED) Web UI not starting, 500 errors.

Archived

This topic is now archived and is closed to further replies.

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.