# Error 400 Bad Request **URL:** \ **Category:** Ignition\ **Created:** [February 16, 2021, 8:26pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480 "2021-02-16T20:26:50Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![diego.villanueva](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@diego.villanueva](https://forum.inductiveautomation.com/u/diego.villanueva)\ **Post date:** [February 16, 2021, 8:26pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/1 "2021-02-16T20:26:50Z")
Every time I try to launch my project using the IDP authentication strategy, I’m able to type my username and password but after I log in I get this: HTTP ERROR 400 Bad Request URI: /data/feerate/callback/ignition STATUS: 400 MESSAGE: Bad Request SERVLET: DataRoutes [http://localhost:8088/data/federate/callback/ignition?code=Pe9jeyli8HfR49NJuGk-Wn5aMjrTj\_ZhCDVmGDHBV8M&state=-CR-5VmRh\_O0K2BdR5ppYcUa1ameWsoMbS\_XjNfT\_Qs](http://localhost:8088/data/federate/callback/ignition?code=Pe9jeyli8HfR49NJuGk-Wn5aMjrTj_ZhCDVmGDHBV8M&state=-CR-5VmRh_O0K2BdR5ppYcUa1ameWsoMbS_XjNfT_Qs) ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [February 16, 2021, 8:47pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/2 "2021-02-16T20:47:52Z")
In which version of Ignition are you running into this issue? What part of Ignition are you logging into? (i.e. Perspective? Gateway Web Interface? Designer? Vision client?) What kind of device are you on? (i.e. Perspective Mobile App on iOS/Android, Perspective Workstation, web browser such as chrome / safari / FF on windows?) Do you have a setup involving multiple Gateways behind a load balancer? ---
**Author:** ![diego.villanueva](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@diego.villanueva](https://forum.inductiveautomation.com/u/diego.villanueva)\ **Post date:** [February 16, 2021, 9:03pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/3 "2021-02-16T21:03:39Z")
1. Version 8.1.0 2. Designer 3. Web browser (Chrome) 4. I don’t think so. ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [February 16, 2021, 9:45pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/4 "2021-02-16T21:45:36Z")
if you set gateway logger `gateway.FederationRoutes` to debug level, and trigger the failed login error again, do you see any messages in the gateway logger? ---
**Author:** ![diego.villanueva](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@diego.villanueva](https://forum.inductiveautomation.com/u/diego.villanueva)\ **Post date:** [February 16, 2021, 10:09pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/5 "2021-02-16T22:09:54Z")
I see this message now: FederationRoutes 16Feb2021 16:09:54 Unable to parse the error redirect URI from the relay state JWT ---
**Author:** ![diego.villanueva](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@diego.villanueva](https://forum.inductiveautomation.com/u/diego.villanueva)\ **Post date:** [February 16, 2021, 10:12pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/6 "2021-02-16T22:12:02Z")
I’m using an ignition IDP ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [February 16, 2021, 10:36pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/7 "2021-02-16T22:36:09Z")
Are you sitting on the login page for a while? I think you only have about 2 minutes from the time you trigger the login in the designer to the time you complete the login before the login request times out. I’m also wondering if there are some browser cookie issues at play here. Did you recently access the Gateway in your web browser using `https://` (SSL/TLS)? If so, and if force secure redirect is not enabled in `Gateway Web Interface > Config > Networking > Web Server`, and if you are trying to login to the designer over insecure `http://`, I could see how your web browser might refuse to honor cookies on the insecure connection. Perhaps try clearing the cookies for the hostname(s) or IP(s) the Gateway is running on from your web browser and try again. Or use one protocol (preferably secure `https://`) in all your interactions with the Gateway… ---
**Author:** ![diego.villanueva](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@diego.villanueva](https://forum.inductiveautomation.com/u/diego.villanueva)\ **Post date:** [February 18, 2021, 1:46am UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/8 "2021-02-18T01:46:28Z")
No, I’m logging in as soon as I launch the project. I tried clearing the cookies for the hostnames the Gateway is running on from my web browser. I also tried accessing the gateway with both https:// and http:// and I still get the same error. This error happens regardless of the browser I use, either Chrome or Firefox ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [May 22, 2023, 8:55pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/9 "2023-05-22T20:55:14Z")
v8.1.27 I'm seeing a slightly, similar problem. I have several Raspberry Pis running Perspective in Chromium in full screen mode (v74.0.3729.157). I was never able to get workstation working on a RPi. I'm authenticating with an Ignition IdP which opens up to authenticate (badge) right after the browser is launched on reboot/startup. If the gateway disconnects for some reason and comes back up, the browser has to be closed and relaunched for the idp to start working again. The badge login screen is still up, but any scan just says bad login information or something like that. If you press the `exit login` button I get the following error. ```auto HTTP ERROR 400 Bad Request URI: /data/federate/callback/ignition STATUS: 400 MESSAGE: Bad Request ``` If the session is authenticated during the disconnect, it redirects to the idp and logs back in without issue. It's only when the project is unauthenticated during the disconnection that renders it useless once the gateway comes back up. With the stations not having keyboards makes it hard to restart the sessions without rebooting all the computers. ---
**Author:** ![Marcus\_Stubbles](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Marcus\_Stubbles](https://forum.inductiveautomation.com/u/Marcus_Stubbles)\ **Post date:** [September 11, 2023, 6:20pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/10 "2023-09-11T18:20:49Z")
Did anyone ever resolve this? I've got one specific user out of dozens who is receiving this same error message and, on turning on the logging, I'm getting the same logged text about the redirect URI. Like the user here, he insists he is not waiting to log in. I haven't yet heard from him to see whether changing browsers helps. ---
**Author:** ![Marcus\_Stubbles](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@Marcus\_Stubbles](https://forum.inductiveautomation.com/u/Marcus_Stubbles)\ **Post date:** [September 18, 2023, 4:27pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/11 "2023-09-18T16:27:32Z")
Okay, not sure why this worked, but it did: A _second_ user got the same error, but then discovered that when he browsed to the site without using his bookmark, it worked. The first user was using a bookmark, too, and on trying without one he could get in, too. So in our case, there was something odd going on with the browser bookmarks. Hope this helps someone . . . . ---
**Author:** ![k.jin](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@k.jin](https://forum.inductiveautomation.com/u/k.jin)\ **Post date:** [January 22, 2026, 8:02pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/12 "2026-01-22T20:02:08Z")
I'm bringing this thread back to life.. I am greeted by this message when I try to launch the ignition designer: HTTP ERROR 400 Bad Request URI: /data/federate/callback/internal/bridge STATUS: 400 MESSAGE: Bad Request It used to work just fine when the designer auth strategy was set to classic but it started throwing the error above when I changed to IdP. Is anyone else having similar issues? Unfortunately, clearing cookie didn't help with the problem. ---
**Author:** ![Alyssa\_Lynch](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@Alyssa\_Lynch](https://forum.inductiveautomation.com/u/Alyssa_Lynch)\ **Post date:** [August 21, 2026, 2:58pm UTC](https://forum.inductiveautomation.com/t/error-400-bad-request/43480/13 "2026-08-21T14:58:19Z")
I thought I would comment on this thread and provide some additional information, as recently our team has encountered this error several times, and there seems to be no absolute solution or cause of the error. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/2/6245f544de9e13f2a8ebe51d3b07c1f4e7607cc9.png) Version 8.3.3 Perspective Web Page Multiple web browsers: Chrome, Firefox Single Gateway Ignition Identity Provider with an AD/Internal Hybrid User source The error occurs after the web page application is launched, and after the user has logged in. We have been unable to pin point what causes the failed login error. According to the users who have experienced this error, they are logging in right away after launching the application. The only common point we have found is that every user that has encountered this error, has used a bookmark; some of which were created on the login screen and some of which created after having logged into the application. Right now the only work around we have found is to clear the browser cookies of the user, and access the project through a fresh link.