Jump to content

(SOLVED) Web UI not starting, 500 errors.


naught

Recommended Posts

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

Link to comment

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

 

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

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.

×
×
  • Create New...