Web UI connection refused. SMB/ SSH access ok

[muddyclapton]

Hello! I'm farily new to this and would really appreciate your help here. Until recently, I had no problem accessing the Web UI either through the the static IP address or tower/main. Since a power outage few months ago I have not been able to access it whatsoever. The browser just shows "connection refused" (see attached screenshot). I can access SMB on my win machine and connect via SSH/putty (attaching the diagnostics here). 

 

I researched all the forum threads but none of the solutions works. Can someone please help? Let me know if I could provide any additional info. thank you!!!

tower-diagnostics-20240424-1914.zip

[bmartino1]

? have you tried to reboot the system since the power outage?

 

you may have that ip address in use on the netwrok form your log:

 

Apr 24 19:06:12 Tower root: Starting Nginx server daemon...
Apr 24 19:06:12 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use)
Apr 24 19:06:12 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use)
Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use)
Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use)
Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use)
Apr 24 19:06:13 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use)
Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use)
Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use)
Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 127.0.0.1:445 failed (98: Address already in use)
Apr 24 19:06:14 Tower nginx: 2024/04/24 19:06:12 [emerg] 5202#5202: bind() to 192.168.1.180:445 failed (98: Address already in use)

whats the current output of terminal command ip a
you may need to change the ip addresses to another ip on your network. One that is not in use on the network.

Edited April 25 by bmartino1

[muddyclapton]

Hi bmartino1,

 

I did reboot the system several times since amongst other things to no avail.

 

whats the current output of terminal command ip a

Not sure what this means but I have set a fixed Ip address 192.168.1.180 from my router.  I'm 100% certain that this address is not used by any other devices in my home network. Do you think reassigning to a different ip address could be the solution?

[muddyclapton]

Here's a screenshot from my router if it helps

[bmartino1]

power cycle all the things. the error even with a permeant address is that 192.168.1.180 is in use on the network.

If you turn off unraid can you ping 192.168.1.180?

Terminal is the command line on unraid at boot or if able to ssh into the system to run linux commands. ip a display all your interfaces and current IP assignments..

You may have grabbed the wrong interface address for unraid static ip... Delete the network config in the config folder on the flash drive and let unraid rebuild the network settings...

[muddyclapton]

Gotcha! Thanks for bearing with a noob.
 

This is what i got from ip a. No idea what I'm looking at. Do I want to go ahead and delete network config file?

 

[bmartino1]

looks like eth0
via br0 is youur mac that you should be using in teh router for dhcpo static mac adress asigment

please confirm that mac ac:15:a2:85:1d:0f
uis set to static ip of 192.168.1.180

[muddyclapton]

I confirm the ip address is set to Unraid server's mac address. 

I also tried your previous suggestion on deleting network.config file and rooting. Unfortunately it did not work. Anything else I should try?

 

[bmartino1]

try in browser to see if you can hit a specfic web page:

What web browser are you using to connect?
https://192.168.1.180/login

http:////192.168.1.180

https://192.168.1.180/Dashboard

in Unraid terminal, what is the output of 
/etc/rc.d/rc.nginx status

 

[muddyclapton]

I tried on firefox, chrome and edge but none worked on any of these addresses. 

 

As for the output you asked here you are:

 

 

[bmartino1]

since nginx x is not running and that is the web server, please run command and see if you can access the web gui:

/etc/rc.d/rc.nginx start

its weird that it didn't start. there may be something else breaking in your instance/setup.

[muddyclapton]

hi first of all just wanted to say a big thank you for guiding me through this.

Following your advise this is what I got. doesnt look like nginx started. 

[bmartino1]

ok. somehow you have something running that is replacing the main bind and accesses.

is it a docker?

https://ioflood.com/blog/docker-stop-all-containers-one-command-to-stop-and-or-remove-every-docker-container/#:~:text=In this command%2C 'docker ps,'docker stop' halts them.&text=Similarly%2C docker ps -a -,docker rm command removes them.&text=Stopping or removing all containers simultaneously might disrupt ongoing tasks or services.
 

All in one command to run:
docker stop $(docker ps -a -q)
 

Please run command

docker ps 

to list all dockers..

Then stop a dockers

docker stop %name_of_docker%

is it a VM?
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-managing_guest_virtual_machines_with_virsh-shutting_down_rebooting_and_force_shutdown_of_a_guest_virtual_machine

To show all VMS:
virsh list --all

shutdown via terminal:
virsh shutdown %VM-name%

Then try to start nginx:
/etc/rc.d/rc.nginx start
/etc/rc.d/rc.nginx restart

did a bad route get setup to the wg tunnel?
lets drop and kick the Wireguard tunnel:
wg-quick down wg*

Edited April 28 by bmartino1

[bmartino1]

If the above doesn't help.

it looks like unraid is running something that has replaced the ports that unraid would use.

if i'm reading your output correctly, it looks like ngnix gave you generic err 98.  port is in use on the unraid system.

So lets kill it via terminal command:

lsof -i :80

 

example of my output of above command.:

root@BMM-Unraid:~# lsof -i :80
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nginx   12275 root    8u  IPv4  14264      0t0  TCP localhost:http (LISTEN)
nginx   12275 root    9u  IPv4  14265      0t0  TCP BMM-Unraid:http (LISTEN)

Then kill all and any apps in the list to do this look at PID #

Command:
I forget the command...
https://docs.oracle.com/cd/E19253-01/817-0403/eoizf/index.html

This should work example:
kill -9 12275

or

kill -SIGKILL 12275

you can also use htop in terminal....

Then try to start nginx:
/etc/rc.d/rc.nginx start
/etc/rc.d/rc.nginx restart

Edited April 28 by bmartino1
fix tested working commands

[muddyclapton]

Following your suggestion here's what I got

 

I confirm no docker is taking the :80 port and I'm not running any VMs.

 

so isof command shows one instance - tailscale docker, and i killed it. 

 

 

After confirming tailscale is killed using lsof command again (nothing shows up), I tried to start nginx but it still showed address in use....

 

 

btw i also tried lsof -i:445 and the output is as follows in case it helps with your further diagnose.

 

 

Kindly let me know if I followed all the steps correctly? Thank you so much sir!

 

Edited Sunday at 03:33 PM by muddyclapton

[bmartino1]

what is the contents of the extra folder on unraid:
/boot/extra# ls
screen-4.9.1-x86_64-1_nerdtools.txz

per other post:

Looks like your tailscale is broken on unraid and is prevening the web gui access.
https://tailscale.com/kb/1080/cli
try to run tailscale down

Then kill the processes if running on port 443 and port 80

then stoped nginx service
/etc/rc.d/rc.nginx stop
 

confirm you got stop message

Then start

/etc/rc.d/rc.nginx start

Edited Sunday at 11:23 PM by bmartino1

[muddyclapton]

Sorry for the late reply I was occupied at work

 

 

--quote--

what is the contents of the extra folder on unraid:
/boot/extra# ls
screen-4.9.1-x86_64-1_nerdtools.txz
--unquote--
 

I'm not quite sure what you meant by this. Is this something I should be looking for in the unraid flashdrive? I tried it in putty but nothing came out of it.

 

 

The <tailscale down> command didnt work, but I managed to kill it with <docker kill> command.

 

At this point I tried the nginx STOP/ START commands but got same error messages as previous post: