This browser is not supported by Splunk after upgrade to 6.4.1 -- any and all browsers, Chrome, IE, you name it?

[bbiandov]

This browser is not supported by Splunk after upgrade to 6.4.1 -- any and all browsers, Chrome, IE, you name it?

To be specific, Chrome is at Version 50.0.2661.102 m and that error still pops up? The un-official fix from the previous versions -- static.html edit does not fix the problem... Essentially we are locked out of the GUI with this bug?

Any suggestions will be appreciated!
Thanks

[dutchguy]

Hi, same problem here, after update to splunklight-6.4.1-debde650d26e-linux-2.6-intel on Ubuntu 12.04 32 bits. I reinstalled splunklight-6.3.3-f44afce176d0-linux-2.6-intel so I could continue using it, awaiting a solution for 6.4.1.

[vsheridan_splun · Accepted solution]

This issue appears to occur with the Linux 32-bit version of Splunk Enterprise 6.4.1. Splunk no longer supports Splunk Enterprise on 32-bit Linux, as of Splunk Enterprise 6.4.0. We accidentally posted this download with the 6.4.1 maintenance release. We have now removed it from the Splunk download site. We apologize for any inconvenience this might have caused you.

Linux customers should use the 64-bit version. If you are not using the Linux 32-bit version and are experiencing this issue, please contact Splunk Support and open a Support case with us.

[stmcmahon_splun]

Hello - I am sorry that Splunk users are having this issue. If Yann's post above is not solving the issue, please open a case. If this is a product defect, we will work to find a solution ASAP. If there is some mis-configuration or other issue that can be solved, we can post here.

Thank you!
Steve McMahon
VP of Support

[leots]

The same issue after upgrading to 6.4.1.
I upgraded 32bit installation on CentOS 6.7.
Now I can't connect to Splunk with either browser.
I tried IE11, Chrome, Edge, Firefox, even Konqueror - neither working.
I tried to clear Java cache as suggested above - doesn't help.
Seems a bug in 32bit installation.

[beginner]

Upgraded Splunk on 32-bit RedHat with package splunk-6.4.1-debde650d26e.i386.rpm. Same problem.

[yannK]

Can it be the javascripts in the cache.

Please try :
A - clear splunk web server cache
on the search-head goto $SPLUNK_HOME/var/run/splunk/appserver,
clear the sub folders i18n and modules
(they will be recreated automatically when needed)
B - clear browser cache
then retry to connect from the client browser

and let us know if this helps.

[philjian]

Installed Splunk 7.0.2.

Users with Chrome 65.0.3325.146 received "This Browser not supported"
Clearing the i18n folders worked.

[mokoborit]

Posted solution above did not work for me. I have the same issue

[hpbrand]

Upgraded 9 splunk Servers (8 x 64-bit, 1 x 32-bit). Problem only appeared on the 32-bit ubuntu system with following install source: splunk-6.4.1-debde650d26e-linux-2.6-intel.deb

[ChrisG]

I can't reproduce the problem on my own local installations on Mac OS or Windows, or on a Linux search head I connect to. What operating system are you using?

[bbiandov]

Any and ALL OSes behave the same, tested client on Windows 7, Ubuntu 16.04 and on my iPhone 6 running 9.3.2 -- same result with Chrome or FF. If you were asking about the server, it's an Ubuntu 12.04 VM. Given the lack of answers I figured there is something here so instead of waiting on diplomacy we reverted back to 6.3 until this issue becomes more transparent and a fix is shared with the community.

[jkat54]

Just because I've added custom messages to the warning message page, and because this might help someone troubleshoot and find a solution. The message given to the browser is found in this file:

/opt/li/splunk/share/splunk/search_mrsparkle/templates/pages/static.html

and here is the code I modified last... note it appears jquery has failed:

<script>
        // If jQuery failed to bootstrap, then assume we have an unsupported browser and display a message.
        // This code must be in a separate script tag so that it will wait for the i18n.js resource to load before executing.
        // NOTE: The 'en-DEBUG' locale relies on jQuery so that cannot be used to test these extractions.
        if(!window.jQuery) {
            var notSupportedEl = document.getElementById('browser-not-supported');
            // NOTE: The following translations must be duplicated in routers/Account.js in order to work correctly.
            // If you make changes to these strings, also update their counterpart in Account.js.
            notSupportedEl.innerHTML = ([
                '<p>',
                gettext('This browser is not supported by Splunk.'),
                '&lt;br/&gt;',
                gettext('Please refer to the list of %s.').replace('%s', '<a href="#">' + gettext('Supported Browsers') + '</a>'),
                '&lt;br/&gt;<font color=red>',
                gettext('In case you run Internet Explorer v9 or later in IE8 compatibility mode, please use F12 to run a Document Mode of IE9 at least'),
                '</font></p>'
            ]).join('');
            var docLinkEl = notSupportedEl.getElementsByTagName('a')[0];
            docLinkEl.href = baseRoute('/help?location=learnmore.systemrequirements');
            notSupportedEl.style.display = 'block';
        }
    </script>

[clivechan]

I hit the same problem using ubuntu