Unable to access web GUI

[APD189]

Hi All,

I'm in need of assistance. I rebooted my unraid server and now I cannot connect to the GUI.

unRAID is running 6.10.0-rc4

I'm able to SSH into the server

I'm not able to access the GUI

It is connected to unRAID.net so that it changes the URL to *************.unraid.net

I'm able to ping it's gateway, but nothing outside of it's local network

I did try another internal VLAN gateway and I'm getting "Destination Host Unreachable"

I believe I'm having a routing issue and need some assistance. Here is the routing table

 

root@UNRAID-1:~# route

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

default ubnt.local 0.0.0.0UG 0 0 0 br0

default 172.16.30.10.0.0.0UG 2 0 0 br4

10.0.1.00.0.0.0255.255.255.128 U 0 0 0 shim-br0

10.0.1.00.0.0.0255.255.255.0 U 0 0 0 br0

10.0.1.1280.0.0.0255.255.255.128 U 0 0 0 shim-br0

172.16.30.00.0.0.0255.255.255.128 U 0 0 0 shim-br4

172.16.30.00.0.0.0255.255.255.0 U 0 0 0 br4

172.16.30.128 0.0.0.0255.255.255.128 U 0 0 0 shim-br4

172.17.0.00.0.0.0255.255.0.0U 0 0 0 docker0

 

root@UNRAID-1:~# ping ubnt.local

PING ubnt.local (10.0.1.1) 56(84) bytes of data.

64 bytes from ubnt.local (10.0.1.1): icmp_seq=1 ttl=64 time=0.171 ms

64 bytes from ubnt.local (10.0.1.1): icmp_seq=2 ttl=64 time=0.148 ms

^C

--- ubnt.local ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1002ms

rtt min/avg/max/mdev = 0.148/0.159/0.171/0.011 ms

 

This was working prior to the reboot I performed today.

 

 

So I just re-added my default gateway back in (route add default gw 10.0.1.1) and I'm now able to ping outside of the local network, but I'm still unable to get to the Web GUI.

 

root@UNRAID-1:/boot/config# route add default gw 10.0.1.1

 

root@UNRAID-1:/boot/config# ping 4.2.2.2

PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.

64 bytes from 4.2.2.2: icmp_seq=1 ttl=56 time=4.30 ms

64 bytes from 4.2.2.2: icmp_seq=2 ttl=56 time=4.09 ms

^C

--- 4.2.2.2 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1000ms

rtt min/avg/max/mdev = 4.092/4.195/4.299/0.103 ms

 

root@UNRAID-1:/boot/config# route

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

default ubnt.local 0.0.0.0 UG 0 0 0 shim-br0

default ubnt.local 0.0.0.0 UG 0 0 0 br0

default 172.16.30.1 0.0.0.0 UG 2 0 0 br4

10.0.1.0 0.0.0.0 255.255.255.128 U 0 0 0 shim-br0

10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0

10.0.1.128 0.0.0.0 255.255.255.128 U 0 0 0 shim-br0

172.16.30.0 0.0.0.0 255.255.255.128 U 0 0 0 shim-br4

172.16.30.0 0.0.0.0 255.255.255.0 U 0 0 0 br4

172.16.30.128 0.0.0.0 255.255.255.128 U 0 0 0 shim-br4

172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0

[APD189]

What I've found is that Nginx is not starting up after reboot. I found this article (https://forums.unraid.net/topic/121072-unable-to-reach-gui/#comment-1106035) and I was able to get it to work (with including the removal of the certificates), but after a reboot, Nginx is not starting up.

 

Now I tried to start up Nginx and I'm getting the following response:

 

root@UNRAID-1:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon...

nginx: [emerg] invalid number of arguments in "return" directive in /etc/nginx/conf.d/servers.conf:36

 

Any idea on how to fix this?

[trurl]

attach diagnostics to your NEXT post in this thread

[APD189]

18 hours ago, trurl said:

attach diagnostics to your NEXT post in this thread

Hi @trurl and all,

 

Looks like I have resolved the issue. I believe the issue is from having two network cards with 2 different IP addresses. With this and using the certificate from unraid.net, I believe my unraid server was the cause.

 

1. SSH to unraid server
2. use_ssl no
   1. sets the SSL use to no
3. /etc/rc.d/rc.nginx start
   1. Start the web server
4. /etc/rc.d/rc.nginx status
   1. Check the status of the web server
5. Access WebGUI
6. Stopped Docker
7. Removed the second IP address on the second network card
8. Go to Settings -> Management Access
9. Set SSL to yes
10. Provisioned new SSL certificate
11. Set SSL to auto
12. Accessed WebGui again.
13. Rebooted to test

 

All is working now.

Edited April 8, 2022 by APD189