- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: GAiA WebUI not working with latest Chrome brow...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
GAiA WebUI not working with latest Chrome browser
My Google Chrome web browser just updated to the latest Version 66.0.3359.117 (Official Build) (64-Bit).
All I see is:
Once I enter my user credentials, the browser's screen goes blank.
Looks like this is the same issue as with Firefox.
Currently this expert mode command seems to help as a first workaround:
cp /web/htdocs2/js/login.js /web/htdocs2/js/login.js.orig; sed -i 's/if( form.isValid() ){/if( form.isValid() ){\nform.el.dom.action=formAction;/' /web/htdocs2/js/login.js
Note: This modification does not survive Jumbo Hotfix Updates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Although it is not on the list of recommended browsers, I've been using Opera with Gaia and SmartView and it seem to be very stable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No update from Checkpoint side on this issue ?!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is an SK on the subject: Gaia Portal shows blank page after log in with Firefox 5x or Chrome 66
The workaround Danny provides above is what we document in the Internal portion of that SK.
If you're still having issues after applying the workaround, please open a TAC case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I have been pushing a few persons on this issue as I was rather amazed by the fact that a RFC from almost 20 years old was discarded and the problem being listed as a browser problem.
Let's face it. RFC 2318 : The text/css Media Type was publised in March 1998 and was documenting something that was allready considered best practises.
I am still pretty mad about the current wording. It's a Check point problem for failing to observe best practises which are even formally described.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The best wording is, "expected behavior", ....from any vendor, really !!!.
Who's point of view, is this "expected behavior" from the programmer logic ( could not possibly think all infinite variations) or the user point view that is trying to accomplish a task....ah, the eternal dilemma.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Would really recommend fixing this. Looks so simple 😕
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks all 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for sharing! The workaround worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, but not sure where to run the command mentioned. Is that in expert mode on each gateway in a cluster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it's an expert mode command that should be executed on each gateway where this is an issue.
In a cluster, that means all members.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. Worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FYI...GAiA WebUI on R80.20 Public EA (Management) does work with the latest Chrome version. The fix described here is already incorporated in R80.20 EA login.js and it's commented with "For supporting firefox56".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The official SK lists the workaround now, FYI.
Also we are looking at adding it to the JHF as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is already part of the ongoinig jumbo take 112
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it is
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Many Thanks !!! Worked !!
Just copied/pasted the command in expert mode and it was fixed instantly !!
Was loosing my mind with this WebUI
I use lastest Firefox and R77.30
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great! This fix is also included in Jumbo Hotfix Take 329 (July 2018) and above on R77.30.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
For Future ease of use i am summarizing this thread,
The issue is documented in SK121373
Relevant fix is included in R80.20 and above
also ported to R80.10 JHF take 112 and R77.30 JHF Take 329
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
God bless you brother !!!