FreeNAS 11.3-U3.1 root can't access anything below "Sharing" in the list on the left

Joined
Apr 23, 2017
Messages
30
Accessing a new install of 11.3-U3.1 on a server previously runing 11.2 successfully via a Windows 10 Firefox browser targeting the FreeNAS IP address on a LAN. Clicking on Dashboard, Accounts, System, ... , Sharing all work as expected, but clicking on anything lower - Services, Plugins, Jails, ... , Shell results in no response at all. We're somewhat stymied, welcoming any ideas.
 

jlpellet

Patron
Joined
Mar 21, 2012
Messages
287
I've seen this on a fresh update & cleared it by clearing browser cache & cookies. Hope this helps.
 
Joined
Apr 23, 2017
Messages
30
Boy, that makes no sense at all, but we'll give it a try. That would imply that making the LAN connection from a different machine would give different results. I'll let you know what happens; thanks.

I just looked on my browser and there were no cookies stored by any freeNAS session (192.168.x.x). The problem occurs on another site, though.
 
Last edited:
Joined
Apr 23, 2017
Messages
30
The owner of the "other site" says he got the problem to go away, but doesn't know how/why.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Accessing a new install of 11.3-U3.1 on a server previously runing 11.2 successfully via a Windows 10 Firefox browser targeting the FreeNAS IP address on a LAN. Clicking on Dashboard, Accounts, System, ... , Sharing all work as expected, but clicking on anything lower - Services, Plugins, Jails, ... , Shell results in no response at all. We're somewhat stymied, welcoming any ideas.
Clear your browser cache or try a different browser. No clue why some people have this problem and others do not.
 
Joined
Apr 23, 2017
Messages
30
As I said earlier, it makes no sense to me. As I understand it (which may be wrong), the virtual console connection ultimately appears to FreeNAS as a local console, so why should it care? Maybe the problem is at the other end, and FreeNAS is just waiting for something it never gets. But, going back up the topic list acts normally. Glad I don't have this problem :).
 
Top