Connecting to NAS... Make sure the NAS system is powered on and connected to the network.

schwartznet

Explorer
Joined
Jul 10, 2012
Messages
58
Just did a fresh install of the latest 11.2U1 and get this screen from every browser. There is no firewall or ports blocked and no AV installed at all.

1548176884022.png
 

schwartznet

Explorer
Joined
Jul 10, 2012
Messages
58
Just this

Code:
2019-01-22 18:53:34    Local7.Info    10.5.10.202    Jan 22 16:53:34 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:34 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 OPR/57.0.3098.116"
2019-01-22 18:53:35    Local7.Info    10.5.10.202    Jan 22 16:53:34 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:34 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 OPR/57.0.3098.116"
2019-01-22 18:53:35    Local7.Info    10.5.10.202    Jan 22 16:53:35 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:35 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"
2019-01-22 18:53:36    Local7.Info    10.5.10.202    Jan 22 16:53:35 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:35 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"
2019-01-22 18:53:37    Local7.Info    10.5.10.202    Jan 22 16:53:37 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:37 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"
2019-01-22 18:53:38    Local7.Info    10.5.10.202    Jan 22 16:53:37 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:37 -0800] "GET /ui/sessions/signin HTTP/1.1" 200 2635 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"
2019-01-22 18:53:38    Local7.Info    10.5.10.202    Jan 22 16:53:38 R720XD-Freenas nginx: 10.5.10.5 - - [22/Jan/2019:16:53:38 -0800] "GET /websocket HTTP/1.1" 101 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"


Another note it seems to work find from L2 on the same network just not over vlan to vlan and there is absolutly no firewall blocking anything and my other three freenas servers on this vlan do not do this. They load fine, very strange
 
D

dlavigne

Guest
Did you ever figure out the cause for this? Perhaps a browser plugin or caching issue?
 

v65

Cadet
Joined
Feb 3, 2019
Messages
3
I just upgraded from 11.1-U7 through the web interface 'Update' feature. I now have the same problem from 64-bit Windows 10 using Firefox 65. Edge 42.17134.1.0 and Midori 0.5.11 .

However, from Firefox 65 on Ubuntu 18.04 no problem at all. I like the new user interface!
 

meku

Dabbler
Joined
May 4, 2014
Messages
34
Just this
Another note it seems to work find from L2 on the same network just not over vlan to vlan and there is absolutly no firewall blocking anything and my other three freenas servers on this vlan do not do this. They load fine, very strange

This problem commonly occurs if websockets are blocked between your browser and the server. Perhaps your network device is not allowing the websocket connection to port 80. Are you connecting to your other freenas servers over http or ssl?
 

v65

Cadet
Joined
Feb 3, 2019
Messages
3
I am connecting with http but only Windows browsers are affected. No problem with BSD or Linux.
 

jasonks

Cadet
Joined
Feb 8, 2019
Messages
2
After struggling with this issue for several months I finally figured it out. I have two sites connected by a VPN and I got the same message when I connected from anywhere but the LAN where the FreeNAS box lives. The only other way I could get into the web UI was to tunnel over SSH (which is why it took so long to solve - the workaround was quicker than troubleshooting). I tried multiple browsers on multiple OSes - same behavior. What finally fixed it was disabling Squid on the remote firewalls. Once I set it to bypass Squid for the FreeNAS everything has been working fine.

Also look at ad blockers and other content filters.
 

v65

Cadet
Joined
Feb 3, 2019
Messages
3
I am glad you found a workaround. It doesn't work for me though. I have both Windows 10 and Ubuntu 18.04 on the same network using the same proxy.pac/wpad.dat for proxy configuration with the same local address bypass and the same version Firefox browsers with the same addons. The Ubuntu machines are still unaffected.

I just tried using Safari on an iPhone and that doesn't work either.

FreeNAS has a problem with the web interface. It clearly is providing an error message to the client it is serving. The message says 'Make sure the NAS system is powered on and connected to the network'. If the NAS is not powered on and connected to the network how would I even see this message? If FreeNAS needs some resource from attached clients or from the network inbetween, the error message should be more descriptive. At the moment the error message is nonsense.
 

nycmaster

Cadet
Joined
Aug 2, 2018
Messages
1
I've been struggling with same issue for 2 weeks and tried disabling squid as per jasonks suggested. Works good if squid is disabled but as soon as I re-enable squid service, then the dreaded message comes back. Researched through squid setting and putting tick mark on here made all work. Squid is running and message no longer show up and able to log into FreeNAS in HQ (I'm in Remote Site). BTW, the screenshot is from PFSense squid setting but I'm guessing something like this exist in other flavor of squid other proxy server???
squid.JPG
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,449
Normally such issue comes from trying to restarting a iocage jail.
Best way to fix it is to restart Freenas.
 

jnasm

Cadet
Joined
Apr 7, 2019
Messages
2
Hi, sorry to barge in so late in this thread, but since I have been seeing this too I wanted to share what the problem and solution was on my side. Now, I use https, not http as some of the other posters so it’s admittedly not exactly the same, that I understand but I hope it might help anyway.

Apparently iOS and macOS react like this when there are untrusted certificates in the chain (like the default self-signed cert). This also affects at least Firefox mobile. What I needed to do on iOS was to to add the root certificate as a trusted profile; for example, send it as an email attachment, click the attachment and then go into settings-general-profiles and install the profile, then go into settings-general-about-settings for trusted certificates and activate full trust. The process is similar on macOS, but Keychain is used to manage the settings.

Note that once the screen locks I see it reverting to the screenshot in the original posting, but just reloading restores the login page and one can proceed as usual. This is a bit of a hassle, but I normally use iOS devices for quick checks so it doesn’t matter to me.

Maybe making sure the certificate chain can be fully validated helps the issue also on other platforms?
 
Last edited:

robb

Cadet
Joined
Mar 27, 2021
Messages
1
I just installed a new TrueNAS 12 u2.1 server. Did some looking around yesterday and powered off. Now I powered on the server again and am confronted with exactly this message: Connecting to TrueNAS ... Make sure the TrueNAS system is powered on and connected to the network.

However, the NAS is on the same subnet as I am.
I am running Fedora 33 on my laptop from wich I try to access the TN webinterface. There are now other firewalls between my laptop and the NAS.
Any suggestions how to tackle this?
 

Simon Bingham

Dabbler
Joined
Sep 21, 2018
Messages
15
1630427157831.png


I'm having same issue address is pingable these are the messages when I tried the GUI,
1630427051009.png


SSH is not working with my usual GUI credentials
 

john60

Explorer
Joined
Nov 22, 2021
Messages
85
A year later, this issue still occurs. TrueNAS-SCALE-22.02.2

The pc with the browser and Truenas scale are on the same lan.

Browner reports "Connecting to TrueNAS ... Make sure the TrueNAS system is powered on and connected to the network."

Truenas scale console was in shell, when I exit shell I get the message "middleware is not responding. Press Enter to open root shell"
So back to shell. reboot nas from shell is not a great solution but works.

Are their logs or something I can collect on Truenas the next time this occurs so the root cause can be identified?
 

Yardi

Cadet
Joined
Jul 28, 2022
Messages
1
I'm having the same issue after a recent update, I'm unable to access the web UI, SSH is no longer available, and even though i can see the ahared folders i can't accee them, The weird thing is that i can still access Next Cloud which is installed vis iocage, can anyone help. Thanks in advance.
 

nyxtyr

Dabbler
Joined
Jun 8, 2022
Messages
15
This just started happening to me. I am unable to delete any plugins or really do anything because it seems the connection keeps dropping.

Been stuck at stopping jail for over 15 mins now
1696257828957.png
this process is usually instant.

Has anyone found a fix for this?
 
Top