Home > Citrix NetScaler, Citrix XenApp, Citrix XenDesktop > Fixing the Citrix Access Gateway blank page in IE 11 (Internet Explorer 11) on your Netscaler

Fixing the Citrix Access Gateway blank page in IE 11 (Internet Explorer 11) on your Netscaler

If you have a Netscaler and are using the Citrix Access Gateway (aka Netscaler Gateway now), you might have users using IE 11 (Internet Explorer 11) complain they are getting a blank page. Chrome and Firefox will work fine but IE11 just doesn’t want to show the login page. A quick work around is to tell the user to view the site in compatibility mode or use a different browser but that will annoy users after some time. You have to make it as easy as possible for your users since not all of them are going to be tech savvy.

The best thing to do is force Internet Explorer into compatibility mode on page load. Just open up the index.html running in flash and the one in your theme:

Flash - /netscaler/ns_gui/vpn/index.html

Theme - /var/vpn/themes/Horizon1/ns_gui/vpn/index.html 

and add the following line in header at the top before the body tag:

<META http-equiv="X-UA-Compatible" content="IE=EmulateIE9" />


You can choose which version of IE to emulate and Stackoverflow has an excellent post on the differences between each here:


In my experience, sticking with emulating IE9 works great with the Access Gateway. Users won’t even know the difference. Hope this helps!

  1. Trevor Prokop
    December 30th, 2013 at 07:10 | #1

    Great solution, thanks for sharing.

  2. December 30th, 2013 at 17:34 | #2

    Glad to help Trevor!

  3. Tony
    January 7th, 2014 at 11:51 | #3

    IE10 works fine with the changes but IE11 miss some header content/logo.

  4. Bob
    January 12th, 2014 at 06:53 | #4

    This change did make the NetScaler page render properly without having to be in compatibility mode, but the Citrix Web Interface 5.4 then asks for the plug-in install (when it’s already installed). Adding the site back to compatibility mode makes the Web Interface work properly.

  5. January 13th, 2014 at 17:02 | #5

    I’m not sure why that is happening to you. I tried just now with Web Interface 5.4 with silent detection enabled and it went right through. The ActiveX Control for detection worked as expected.

  6. andyH
    January 14th, 2014 at 13:07 | #6

    Nice workaround for /vpn/index.html, but there is some more stuff, connecting to a WI 5.4 that does not work. silentdetection.aspx, default.aspx, launcher.aspx, …?
    Who knows what exact pages need this META- IE9 Tag?

  7. January 14th, 2014 at 15:47 | #7

    I was unable to replicate the problem on WI 5.4, it works normally for me. You can try including the IE9 emulation line to the header code for those pages. If I remember right all those pages should have an include file at the top. Keep digging backward until you find the include file with the HTML headers and drop the IE9 emulation line in it. It should work. I can try looking for the exact files that need to be modified later in my lab.

  8. Drshutt
    February 12th, 2014 at 12:10 | #8

    Did anyone find the file that needs to be updated on WI 5.4. I am also having this issue. When a user clicks on a published app it prompts them at the bottom of the page to save or open the .ica file.

  9. Byron
    June 2nd, 2014 at 09:16 | #9

    Does anyone know what needs to be modified to fix this for the change password page? Thanks!

  10. DaveT
    July 28th, 2014 at 05:55 | #10

    Hi Guys,
    Did anyone fix this for when the plugin detection fails after the Netscaler fix is applied?

    For me, I get as far as downloadNative.aspx.

    I’ve tried adding the IE9 header info to various places, including the web.config as per here – http://blog.codefluententities.com/2012/09/28/how-to-enable-ie-9-compatibility-mode-for-your-website/ – but I can’t get it to past the downloadNative.aspx page.

    Any thoughts?

    Cheers guys!

  11. Dennis Gamboa
    August 6th, 2014 at 06:58 | #11

    Hi All, I experienced this error when upgrading my IE to ver11. What I did was click Tool then click Compatibility view settings then add the your website and it resolved the issue. Hope this helps. Thanks.

  1. No trackbacks yet.

NOTE: Due to increased spam, your comment may not immediately appear on the site until validated.