Installation

After upgrade to Splunk 6.2, how do I resolve error "This browser is not supported by Splunk" using the latest version of Internet Explorer?

Engager

Hi today i upgraded the office splunk enterprise server to 6.2

Everything when ok, but now the persons that need to see the splunk for Reports/Audits etc all have this error
"This browser is not supported by Splunk.
Please refer to the list of Supported Browsers."
We use the latest Internet Explorer but ... and here is where i think the problem is.
Because of other internal apps we need to setup all our IE to "compatibility mode" to work with our older apps

Is there a way around this error ?
Because i can't change the compatibility mode in IE or else our older apps wont load....

Here is a screenshot

Labels (2)

Path Finder

I encountered the same issue.

Try going to IE settings, select Compatibility View Mode. Remove Splunk from the list of website and unselected the checkbox option for "Display intranet sites in Compatibility View".

This solved my problem. 🙂

0 Karma

New Member

It appears that this problem is fixed in Splunk 6.2.1.1 and later.

0 Karma

Explorer

Are you sure it is fixed? Its not mentioned in the changelog for 6.2.2, and no 6.2.1.1 version is available.

0 Karma

Splunk Employee
Splunk Employee

6.2.2 is available. It is also fixed there.

0 Karma

Explorer

My question was if Splunk can't still support IE8, its just they decided to enforce it without any reason (other than update of jQuery 2 - which has exactly same functionality as 1.10 series but breaks compatibility with older browsers). So for me it is not fixed.

0 Karma

Explorer

Is there any workaround to allow IE8 work with 6.2.x ? It checks if jquery can be initiated, but naturally to Splunk developers, they did it in so obfuscated way that its hard to find how to switch to 1.X jquery (although functionally it the same as 2.X but it does support older browers).

0 Karma

SplunkTrust
SplunkTrust

Please ask the administrator of your group policy to disable whichever settings are applied in /Computer Configuration/Policies/Administrative Templates/Windows Components/Internet Explorer/Compatibility View/ (which could take some searching your Group Policy Objects) and instead configure only "Use Policy List of Internet Explorer 7 sites" to enable compatibility mode on those sites that need it on, leaving all others alone.

In our case we had "Turn on Internet Explorer Standards Mode for local intranet" enabled, meaning it was ON for any site on our local network and couldn't be disabled. We're testing GPO changes ATM with that NOT configured and instead using the setting above to apply those settings to the 3 or 4 sites internally that need it. This has worked fine on the test people.

Splunk Employee
Splunk Employee

Unofficial fix. Make a copy of any file before you change it.

We found that if you modify:
$SPLUNKHOME/share/splunk/searchmrsparkle/templates/pages/static.html

After the head tag add:

<meta http-equiv="X-UA-Compatible" content="IE=edge" />

then around line 79 change the line to (comment out the line):

//       document.write('<meta http-equiv="X-UA-Compatible" content="IE=edge" />');

You don't have to change the setting.

Path Finder

If IE9 is set to use compatibility mode for intranet sites, then this header tag will not override that setting. (http://stackoverflow.com/questions/3726357/why-does-ie9-switch-to-compatibility-mode-on-my-website)

According to Microsoft:
"By default, Compatibility View is enabled for the Intranet Zone, helping to ensure that line-of-business applications work without needing additional modification." (https://technet.microsoft.com/en-us/library/jj822325.aspx)

0 Karma

Engager

I have made this change however it does not resolve the issue, neither does turning off compatibility view or changing to default IE9 mode.

0 Karma

New Member

I don't seem to see $SPLUNKHOME/share/splunk/searchmrsparkle/templates/pages/static.html. Is this supposed to be a file in Splunk 6.2.1?

Within that .../pages/ subfolder, I only see the following files: app.html, base.html, redirect.html, system.html

0 Karma

Splunk Employee
Splunk Employee

This is a problem we have seen with 6.2.1 (or 6.2). We didn't see this problem in 5.0.x.

0 Karma

New Member

rmorlen - I'm interested in your unofficial fix. However, I cannot find the file you mentioned.

0 Karma

Splunk Employee
Splunk Employee

Are you running Splunk 6.2.x? The file doesn't exist in 5.0.x.

0 Karma

New Member

I'm running 6.2.1, but cannot find the file.

0 Karma

New Member

My mistake. Found the file and tried this fix (changing static.html), but it does not resolve the issue.

0 Karma

Engager

This is an issue that needs to be resolved. We did not have any browser issues prior to the upgrade to 6.2, now we have multiple users with this issue and the F12 fix is only temporary due to corporate GPO's and does not always work. Please revert the changes made in this version that broke the functionality of Splunk.

Splunk Employee
Splunk Employee

Compatability mode causes IE 11 to act as IE 6 7 8, which are not supported versions of IE as of Splunk 6.1. Various problems existed in 6.1 when using IE in compatibility mode, though it was possible to use the product with a degraded experience although many users were unaware of the cause of the degradation.

For a variety of reasons, the number of problems with using this non-supported browser configuration increased in 6.2, and this message is produced as a result.

We recommend that users use IE 9 or higher if using IE, and use it in a mode that does not behave as the unsupported revisions 6, 7, or 8.

0 Karma

Splunk Employee
Splunk Employee

I have added this verbiage to the docs:

Do not use Internet Explorer in compatibility mode when accessing Splunk Web. If you do, Splunk Web warns you that your browser is not supported. If you must use IE in compatibility mode, then use another supported browser for Splunk Web.

Splunk Employee
Splunk Employee

If you wish to object to this decision, or the outcome (as you indicate), you can certainly do so, but an answer in Splunk Answers won't really get you any traction. I suggest discussing the problem in how it affects your deployment with your sales representative as a starting point.