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.

WebGUI inaccessible on fresh install?

Featured Replies

Just installed 6.3.5 on a new USB, booted server, it gets an IP which I can ping and SSH into, yet can't access the webgui.  I've tried IE, Chrome, and Firefox as well as accessing from multiple PC's on the same subnet.  

 

ifconfig shows the following:

 

bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2620  bytes 271661 (265.2 KiB)
        RX errors 0  dropped 21  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.10.114  netmask 255.255.255.0  broadcast 10.0.10.255
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2595  bytes 233601 (228.1 KiB)
        RX errors 0  dropped 7  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2620  bytes 271661 (265.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xdf100000-df17ffff

eth1: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf300000-df320000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.255.255.255
        loop  txqueuelen 1  (Local Loopback)
        RX packets 2  bytes 140 (140.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 140 (140.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

Edited by IamSpartacus

12 minutes ago, IamSpartacus said:

Just installed 6.3.5 on a new USB, booted server, it gets an IP which I can ping and SSH into, yet can't access the webgui.  I've tried IE, Chrome, and Firefox as well as accessing from multiple PC's on the same subnet.  

 

ifconfig shows the following:

 


bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2620  bytes 271661 (265.2 KiB)
        RX errors 0  dropped 21  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.10.114  netmask 255.255.255.0  broadcast 10.0.10.255
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2595  bytes 233601 (228.1 KiB)
        RX errors 0  dropped 7  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 2620  bytes 271661 (265.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 369  bytes 33015 (32.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xdf100000-df17ffff

eth1: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
        ether d0:50:99:c2:74:85  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf300000-df320000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.255.255.255
        loop  txqueuelen 1  (Local Loopback)
        RX packets 2  bytes 140 (140.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 140 (140.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

 

This shows the IP of: 10.0.10.114

 

does:  http://NAS:80 work http://unraid:80 ?  or http://10.0.10.114

 

If not,  check the logs or even post them here for any emhttp errors.   

  • Author
7 minutes ago, fmp4m said:

 

This shows the IP of: 10.0.10.114

 

does:  http://NAS:80 work http://unraid:80 ?  or http://10.0.10.114

 

If not,  check the logs or even post them here for any emhttp errors.   

 

Yes http://10.0.10.114 is how I'm trying to access it.  Where can I find logs via CLI?

  • Author

Found syslog in /var/log but don't see anything referring to emhttp in there.

SSH to the server and type "diagnostics", that will place a zip file in the "logs" directory on your flash drive. Move the flash drive to your pc and attach the zip file to this thread.

  • Author
8 minutes ago, ljm42 said:

SSH to the server and type "diagnostics", that will place a zip file in the "logs" directory on your flash drive. Move the flash drive to your pc and attach the zip file to this thread.

 

I'm confused.  I SSH'd into the server, typed diagnostics, it confirmed it created the zip file in /boot/logs.  I navigated to that directory, did an ls -la and saw the file.  But when I powerdown my server and put the USB into a windows PC, there is no logs directory and thus no diagnostics zip file.

  • Author

It's def. the USB flash drive.  The USB key I've been trying for this fresh install is a Cruzer Fit USB 3.0 key.  I have a Cruzer Fit USB 2.0 key that I just tried and it now works fine.  Both plugged into a USB 3.0 header on the MB.  Strange.

Edited by IamSpartacus

The USB 3 drive is probably ok, for whatever reason unRAID works best with USB 2. I'd recommend moving the USB 2 key to a USB 2 slot if you can.

  • Community Expert

There have been several cases in the past, where Flash Drive inserted into the USB3 slots end up getting disconnected.  It seems to be related to certain MB's and BIOS.  For that reason, many of us have suggested that the boot Flash Drive always be installed into a USB2 slot.  (USB2 slots are the one with the Black plastic insert.) The Flash drive (for the most part) is only used during the actual boot process and during shutdown so the slower read/write speed of USB2 is inconsequential to the overall performance of unRAID.

  • Author
2 minutes ago, Frank1940 said:

There have been several cases in the past, where Flash Drive inserted into the USB3 slots end up getting disconnected.  It seems to be related to certain MB's and BIOS.  For that reason, many of us have suggested that the boot Flash Drive always be installed into a USB2 slot.  (USB2 slots are the one with the Black plastic insert.) The Flash drive (for the most part) is only used during the actual boot process and during shutdown so the slower read/write speed of USB2 is inconsequential to the overall performance of unRAID.

 

The problem is my internal USB header is USB 3.0 and I'd like to use it.  I'm going to look in the BIOS and see if I can disable USB 3.0 on it.

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.