12.0 U2 and Firefox not liking each other.

[Dirk]

Decided to move away from Chrome after endless captchas trying to go anywhere from Google lately.

Two Freenas servers running the latest and the latest Firefox.

Repeated stalls at "make sure the server is powered on" before login screen. Clearing cache does not help. Using about:support in Firefox leads to a "clear startup cache" button that will temporarily solve the issue. Firefox has been removed and re-installed, with no effect.

the more concerning/annoying problem in Firefox is that no shell will load. The shell in the left menu of the GUI, any shell from a jail, and even the "display system processes" button all end with a blank terminal screen, but no text inside it. The main shell terminal will display a button at the bottom marked "Reconnect" that has no effect

All of this does not manifest itself in Chrome.

Obviously from the above we can assume a Firefox issue, but not sure where to look. I would think maybe the community may have had the same experience?
Thanks

 

[Dirk]

Another thing to note. Reboot Freenas under Chrome results in screen dropping back to "make sure server is on " screen and after the boot finishes the login screen comes up (as expected). Under Firefox it just stays at the make sure server is powered on.

 

[0nighthawk0]

I also have issues with Firefox and the https caching - it keeps saying that the cert is no longer valid after each reboot.

So atm i'm using just the http login and ssh to get around this.

Still not going anywhere near the excrement that is Chrome though - firefox has been better than Chrome for me in various niche cases over the years so would like to know what is going on and how we can fix it.

 

[Dirk]

Not using an https login here. This is happening on an http login.

 

[0nighthawk0]

To be honest i'm using Firefox and definetely don't have the issues you are having with shell, etc.

Do you have addins on that may be interfering? I found NoScript and Decentraleyes caused problems.

I run ublock origin, and https everywhere...plus i've customised about:config a bit, i also chose to trust my TrueNAS sites and the only issue i have is the https reload/cache issue. 12.0-U1.1 here tho.

 

[Dirk]

Where did you put your trusted sites hawk?
Thanks

 

[0nighthawk0]

Just under the exceptions for privacy and security. Notably for notificatons, blocking pop-up windows and addons. You shouldn't need to do this though.

I have custom settings for quite a bit though.

I just tried a vanilla firefox from another machine and i'm not getting the issue you are, although it isnt auto refreshing the page when i know its available... (tested by switching wifi networks and later switching back).

 

[0nighthawk0]

Also maybe not relevant but... the http://truenas.local/ui/sessions/signin page actually doesn't refresh for me. When i'm on the edge of my wifi connection the client loses communication and when back in range instead of going back to the login screen it stays on the "make sure its on and connected" page. When i click refresh it doesn't work either. but when i remove the /sessions/signin bit and just hit http://truenas.local/ui/ it will bring back the login page.

 

[Dirk]

I tried modifying the exceptions, and the abreviated url you suggested. It still stalls at make sure machine is powered on. Getting it to the make sure dialog and then go to about:support and then on the right clear startup cache and a refresh of the screen. Do it in different tabs the the login screen stays where it was.

 

[Newfoundland.Republic]

I usually use Chrome but I tried Firefox. No issues with Firefox 85.0.1 (64-bit) (Ubuntu 20.10). Everything seems to work correctly in the GUI.

--- Edit ---
The version of Chrome I use is Version 88.0.4324.182 (Official Build) (64-bit)

 

[Dirk]

Thanks for the input newfoundland. This is just baffling to me with one of the servers being a new install, Chrome working fine, Firfox is a new install, and the terminals are just plain broke.

For poopoo and giggles I'm going to try and access with Firefox from my Ubuntu 20 box (instead of mt Win 10 that I'm doing this on) and see what happens.

 

[pschatz100]

I have been using Firefox almost exclusively from Windows 10 for years without a problem, other than the need to clear the cache after I updated to TrueNAS 12. Current version of Firefox I have installed is 86.0 64bit.

One thing I would try is to disable any add-ons you have and see if that makes a difference. I also presume that you don't have anything running in your TrueNAS instance that would affect loading web pages. Right? You might also try changing the TrueNAS theme to see if that makes a difference.

Firefox is fussier about security than is Chrome or Edge.

 

[Dirk]

Thanks pschatz. I've been doing computers for a long time and can usually help myself. I generally will invest 6+ hours trying to resolve something and then ask for help. I don't think it's on the Freenas side as both exibit the same problem with one of them a fresh install. I've eliminated the usual suspects and turned off Malwarebytes and the virus software as well as removing and reinstalling Firefox. There were no add-ons in the first install of Firefox or the present.

The oddest thing of it all is that it effects the terminal windows more than anything. They startup fine, but are blank. The main shell off the left menu shows a button at the bottom saying Restore but has no process when clicked

 

[Apollo]

I only use Firefox, but I mostly connect to FreeNAS/TrueNAS using IP addresses. Have you tried that?

 

[Dirk]

I only use Firefox, but I mostly connect to FreeNAS/TrueNAS using IP addresses. Have you tried that?

Thanks apollo. Both Freenas servers AND my Win 10 client are on the same local lan and have always been accessed by IP.

 

[Apollo]

If you have access to the Web interface, you could try adjusting the settings under the "System" => "General" => GUI

 

[Apollo]

Is it possible you have the "https://XXX.XXX.XXX.XXX" in the URL? if so try removing the "https://" and only use the IP address?
Have you tried by any chance clearing the cookies?