Been using Unraid for well over a year and not noticed this before. Reboot/shutdown does not help.

 

When using IE or Firefox to access the Webgui only a blank page will load.

Using version 4.7, Windows 7 x64 Ultimate, IE 9 and/or Firefox 6.x

 

URL is http://icarus/main.htm

 

Appreciate your help.

Syslog attached.

Thanks - Meerkat

 

Update: Google Chrome reports

Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

syslog.txt

Try connecting to http://IP.address.of.server

Try connecting to http://IP.address.of.server

 

My network is setup as follows:

 

# Generated settings:

 

USE_DHCP=no

IPADDR=10.0.0.69

NETMASK=255.255.255.0

GATEWAY=10.0.0.1

HWADDR=00:1A:92:D3:EE:7B

DHCP_KEEPRESOLV=no

DNS_SERVER1=10.0.0.1

 

http://10.0.0.69 gives same result.

 

What is interesting is this:

root@Icarus:~# ping icarus

PING Icarus (127.0.0.1) 56(84) bytes of data.

64 bytes from Icarus (127.0.0.1): icmp_seq=1 ttl=64 time=0.014 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=2 ttl=64 time=0.019 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=3 ttl=64 time=0.018 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=4 ttl=64 time=0.019 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=5 ttl=64 time=0.018 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=6 ttl=64 time=0.018 ms

64 bytes from Icarus (127.0.0.1): icmp_seq=7 ttl=64 time=0.018 ms

 

Shouldn't ping return 10.0.0.69?

From Windows:

 

C:\Users\user>ping icarus

 

Pinging icarus [10.0.0.69] with 32 bytes of data:

Reply from 10.0.0.69: bytes=32 time<1ms TTL=64

Reply from 10.0.0.69: bytes=32 time<1ms TTL=64

 

Ping statistics for 10.0.0.69:

   Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),

Thanks for the quick response.

-Kat

 

 

Enter "ifconfig"

I just ran into this exact same issue. I can get unmenu to load but not the normal unraid webgui.

Enter "ifconfig"

 

Thanks! Results are:

root@Icarus:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:1a:92:d3:ee:07

          inet addr:10.0.0.69  Bcast:10.0.0.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:4964 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1446 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:775854 (757.6 KiB)  TX bytes:377822 (368.9 KiB)

          Interrupt:26 Base address:0x4000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:102 errors:0 dropped:0 overruns:0 frame:0

          TX packets:102 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:8568 (8.3 KiB)  TX bytes:8568 (8.3 KiB)

 

This is very odd mystery...nothing changed on my network in over a year and not had any issues.

-Kat

is "emhttp" still running?  (if not, it might have been killed if you are running low on memory)

 

Type

ps -ef | grep emhttp | grep -v grep

to see if it is.

 

is "emhttp" still running?  (if not, it might have been killed if you are running low on memory)

 

Type

ps -ef | grep emhttp | grep -v grep

to see if it is.

 

Here is the output.

root@Icarus:~# ps -ef | grep emhttp | grep -v grep

root      1462    1  0 18:16 ?        00:00:00 /usr/local/sbin/emhttp

root@Icarus:~#

 

Thanks for the quick response,

Kim

I can't find any documentation on the network entry "BDHCP_KEEPRESOLV=no". I have not changed this entry but something I should investigate further?

Thanks everyone for your input.

-Kat

 

OK..found the culprit: ESET NOD32 5 antivirus software. When I disable the web scanning on port 80 I am able to load the Unraid GUI with no issues! I had just upgraded to NOD32 5.0 when this started and should have looked there sooner.

 

NOD 32 5.0.93.0 on Windows 7 Ultimate X64.

 

Solution was as follows:

1) Right Click on NOD32 icon on taskbar and select "Advanced Setup"

2) Expand "Web and Email".

3) Expand "Web access protect".

4) Highlight "HTTP, HTTPS" and uncheck "Enable HTTP Checking".

5) Click ok.

 

Thank you everyone for your assistance

-Kat

Got the same issue with Eset Smart Security 5. Thanks for pointing me to the solution.

 

I just added the IP Adress of my server in the excluded IP adresses under the Protocol Filtering menu.

 

This allows keeping Eset's protection except for the Unraid server.

 

Thanks, had the same issue with new eset. 

Thanks, I had the same problem with Sophos Antivirus 10.0.

 

Adding the IP address of the unRaid machine to the exclusions list solved the problem for me.