[SOLVED] Can not access unRAID's nor unMENU web interface

[sakh1979]

All -

 

All was running fine till this evening. But, I just noticed that I can not access neither unRAID's nor unMENU's web interface at 192.168.0.100, or 192.168.0.100:8080.

 

I turned off unRAID by holding the power off button for few seconds, and after restarting it it started parity check. I don't know why it started the parity check since I did use the power button to turn the server off!

 

I don't know where the problem lies at, because I telnet into my unRAID box and executed: `netstat -an | grep 80` and `netstat -an | grep 8080`, these commands suggest that the unRAID and unMENU's web interface should be running fine.

 

At first, I thought the problem was my wireless router, I use D-LINK's DIR-655. I upgraded it to the lastest firmware version 2.07NA, unfortunately that did not improve the situation.

 

I don't know what is causing it, but I can not access internet wirelessly from my laptop at all. I am able to connect to the internet via my Mac, which is it connected to the wireless router via cat-6 cable.

 

I don't think its the unRAID server that is causing it, but I can not put my finger on the problem. I hope someone on this forum might have an idea?

 

Oh, by the way, I can perfectly access unRAID from my Mac, i.e. I can mount all the User's Share on my Mac via SMB protocol. But, still even from my Mac I can not access the web UI.

 

Just in case for the curious minds, I have attached the syslog in the attachment.

 

Thanks,

Sagun

syslog.txt

[ShangHangin]

 

A couple of my own learnings:

1.  Using the power button does not properly shut the array down and unmount the disks.  unRaid will run a parity check upon restart.

 

2.  For the menus not running, telnet into your system and run the following at the command line to restart the unRaid webGUI

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

3.  For unMenu:

 

cd /boot/unmenu

uu

 

Hope it helps, as I have had the same problems at times

 

SH

[sakh1979]

ShangHangin -

 

Thank you for your reply.

 

/boot/unmenu/uu brought the unMENU up.

 

But, I get this message when I try to bring up unRAID web gui with the commands you provided:

 

root@Tower:~# killall emhttp

root@Tower:~# nohup /usr/local/emhttp &

[1] 6706

root@Tower:~# nohup: ignoring input and appending output to `nohup.out'

nohup: cannot run command `/usr/local/emhttp': No such file or directory

 

[1]+  Exit 127                nohup /usr/local/emhttp

root@Tower:~#

 

 

Thanks,

Sagun

[Joe L.]

ShangHangin -

 

Thank you for your reply.

 

/boot/unmenu/uu brought the unMENU up.

 

But, I get this message when I try to bring up unRAID web gui with the commands you provided:

 

root@Tower:~# killall emhttp

root@Tower:~# nohup /usr/local/emhttp &

[1] 6706

root@Tower:~# nohup: ignoring input and appending output to `nohup.out'

nohup: cannot run command `/usr/local/emhttp': No such file or directory

 

[1]+  Exit 127                nohup /usr/local/emhttp

root@Tower:~#

 

 

Thanks,

Sagun

/usr/local/sbin/emhttp

you tried

/usr/local/emhttp

it does not exist...

[sakh1979]

Thanks Joe L. that worked.

[Zangief]

Hmmm this didnt seem to do anything for my unraid menu... but I guess this thread was several versions out of date...

[JonathanM]

59 minutes ago, Zangief said:

I guess this thread was several versions out of date...

Five years??? Yeah, the entire unraid ecosystem has changed. Nothing in this post is relevant to 6.3.3

[Zangief]

As I've discovered to my detriment... A drowning man will still grab onto anything he can find!

[Can0n]

I found this old post as i was trying to find out why my gui crashed as i was trying to bring my newly crashed VM back up.  i was able to killall emhttp and do the nohup command the cd/boot/unmenu <-- the unmenu doesnt exist on v6.3.5 any help restarting the webgui without rebooting would be great as I just replaced a data drive and its still rebuilding contents.

 

[bonienl]

Since unRAID v5 the emhttp process is not restartable and the only way to make it work again is rebooting your server.

 

Also unmenu should not be used when running unRAID v6 or later.