# Ignition not opening in Firefox and incognito mode **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [December 12, 2023, 12:21pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024 "2023-12-12T12:21:40Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [December 12, 2023, 12:21pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/1 "2023-12-12T12:21:40Z")
We recently realized Ignition perspective administrative web page (same with any Ignition project but for simplicity we will say the admin page) cannot be loaded in Firefox in incognito mode. To be more precise the website in question after 5 or more minutes is able to open in Firefox in incognito mode but it takes so many minutes we can say for all practical purposes it is not. We tried to debug with curl to be as browser agnostic as possible and realized that Ignition makes heavy use of HTTP 302 redirects to the point that even following the redirects ends in an endless cycle (we talk about 50 or more redirects), for instance: ```auto $ curl -L --max-redirs 15 http://ourscada.example.net/web % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 curl: (47) Maximum (15) redirects followed ``` we have another Ignition installation (slightly different version number) which has the same 302 endless redirects problem with curl but can be opened in Firefox in incognito almost instantly. Can someone tell us what is going on? it is hard enough to debug Ignition applications as they are, but without the assurance of at least having a working incognito mode the problem is amplified ten fold because we don't know what is cached and what is not. We previously used Chrome but some things are rendered differently in Firefox and we now have to debug both in Chrome and Firefox (potentially Edge as well). ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 12, 2023, 2:38pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/2 "2023-12-12T14:38:17Z")
~~Those 302s aren't coming from Ignition, they're coming from some other middleware related to your hosting environment, guaranteed.~~ I was wrong. ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [December 12, 2023, 3:00pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/3 "2023-12-12T15:00:56Z")
Hi, I just checked on a local Ignition installation: > $ curl -L --max-redirs 15 [http://localhost/web](http://localhost/web) > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > curl: (47) Maximum (15) redirects followed anyway we don't have any middleware: we have windows machines with ignition installed on AWS EC2, nothing in between. I checked through company connection and via an hotspot on my phone, same behaviour. I also checked it wasn't due to the fact we were using the IDP which could potentially make weird redirects but my localhost installation has no IDP enabled (it uses the default ignition authentication IDP). ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [December 14, 2023, 9:06am UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/4 "2023-12-14T09:06:18Z")
any insight? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 14, 2023, 10:16pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/5 "2023-12-14T22:16:57Z")
Well, you're right and I was wrong - there is a problem with the `/web` endpoint specifically causing an infinite redirect loop. From your original post though, it's a little unclear - this is also affecting you on e.g. a Perspective page? ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [December 15, 2023, 8:26am UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/6 "2023-12-15T08:26:59Z")
Hi, I just checked and it seems the redirect loop happens on the main page of a project as well. curl -L --max-redirs 15 [http://localhost/](http://localhost/) % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 422 100 422 0 0 881 0 --:--:-- --:--:-- --:--:-- 881 100 101 100 101 0 0 179 0 --:--:-- --:--:-- --:--:-- 179 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 422 100 422 0 0 553 0 --:--:-- --:--:-- --:--:-- 553 100 101 100 101 0 0 114 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 422 100 422 0 0 392 0 0:00:01 0:00:01 --:--:-- 392 100 101 100 101 0 0 78 0 0:00:01 0:00:01 --:--:-- 78 curl: (47) Maximum (15) redirects followed ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 15, 2023, 4:21pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/7 "2023-12-15T16:21:39Z")
So, it appears that we constantly redirect you if you don't provide us with a (valid) JSESSIONID cookie. You can e.g. tell `curl` to store one with the `-c` flag - so: ```auto ❯ curl -L 'http://localhost:8088/' curl: (47) Maximum (50) redirects followed ``` Whereas with `-c`: ```auto ❯ curl -L 'http://localhost:8088/' -c cookies.txt (omitted ...) ``` I don't know enough about `curl` to know if there's a way to recycle cookies across redirects without requiring an actual file for storage. My guess is your Firefox private session is set to a stricter mode that doesn't accept any cookies, even to store temporarily while the session is open, and that's why you get into a redirect loop. My Firefox, even in private mode, is able to connect to `localhost:8088` just fine, so that might be a setting you can configure. This is possibly a bug (I don't really know the internal mechanisms well enough to judge confidently) but even if it we do treat it as such, it'll be some time before we can issue a fix, so you may as well try to work around it. ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [December 18, 2023, 2:02pm UTC](https://forum.inductiveautomation.com/t/ignition-not-opening-in-firefox-and-incognito-mode/83024/8 "2023-12-18T14:02:08Z")
Ok, notice the firefox I have is the latest (120.0.1 64-bit) and I just installed it from scratch just to be sure no weird configurations are present. So people might experience this behaviour with any Firefox 120.0.1 browser in incognito mode and future releases. Thank you for your time.