Unable to access web GUI

[rmilyard]

So rebooted my unraid server today. After it rebooted I can access all my dockers like Plex, sabnzb and etc but when trying to go to main dashboard of server getting This site can't be reached error. I have been running this server for few years so it's not a new install or anything.

[Squid]

From the local keyboard / monitor, type in diagnostics and then post the resulting file from the flash drive here (logs folder)

[whauk]

I had the same problem, so I will use the chance to post my diags file here.

Situation was: I could access all dockers (they were running), but not the Unraid GUI.

Assuming this was a minor error, I rebooted my Unraid machine. Now I can't access the GUI either but on top of that I also can't start the dockers anymore because I can't start the array.

(#!/bin/bash

CSRF=$(cat /var/local/emhttp/var.ini | grep -oP 'csrf_token="\K[^"]+')

curl -k --data "startState=STARTED&file=&csrf_token=${CSRF}&cmdStop=Stop" http://localhost/update.htm

did not work as far as I can tell - "curl: (7) Failed to connect to localhost port 80: Connection refused" probably because my Unraid listens on port 8008, port 80 being required for PiHole)

If that's the reason how do I change it?

nas-diagnostics-20201022-1351.zip

Edited October 22, 2020 by whauk
Some clarifications

[Squid]

9 minutes ago, whauk said:

CSRF=$(cat /var/local/emhttp/var.ini | grep -oP 'csrf_token="\K[^"]+')

curl -k --data "startState=STARTED&file=&csrf_token=${CSRF}&cmdStop=Stop" http://localhost/update.htm

With the login screen now, those commands probably do not work anymore.

 

11 minutes ago, whauk said:

port 80 being required for PiHole

Usually, you would put PiHole on it's own separate IP address.  Simplifies everything, and I believe the templates are all set up that way.

 

12 minutes ago, whauk said:

If that's the reason how do I change it?

Edit /config/ident on the flash drive and change the port, (also edit docker.cfg and set it to not start the service)

 

What is this line in your "go" doing? Probably should remove it.

cp -r /usr/local/emhttp/plugins/webGui/phaze.page /usr/local/emhttp/plugins/dynamix

 

[whauk]

1 hour ago, Squid said:

With the login screen now, those commands probably do not work anymore.

 

Usually, you would put PiHole on it's own separate IP address.  Simplifies everything, and I believe the templates are all set up that way.

 

Edit /config/ident on the flash drive and change the port, (also edit docker.cfg and set it to not start the service)

 

What is this line in your "go" doing? Probably should remove it.

cp -r /usr/local/emhttp/plugins/webGui/phaze.page /usr/local/emhttp/plugins/dynamix

 

Commands: No, they did not work - I only found them as the (chronologically) latest potential solution to my problem. Ticked off.

The PiHole docker is on its own separate IP. However, according to the video howto, it still requires port 80 on the Unraid machine. So I changed the Unraid http port to 8008 using the GUI last night. Unraid rebooted without any hassle after that and I could start the array.

Line in "go": No idea either. Didn't touch it ever. Don't know what it's been doing but it's been sitting there without doiung any harm so far.

 

Edit: I'll be damned - it worked, the GUI is back up. The "go" line made no difference; it was the port. I don't get it - why can I change the port then?

Edited October 22, 2020 by whauk

[Squid]

45 minutes ago, whauk said:

why can I change the port then?

You don't need to with PiHole on it's own IP.  

[whauk]

Thanks, I'll check on that.

But why can I then, why isn't it hardwired when I have GUI problems after changing it?

And thanks very much for the help.