# Mobile application **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [July 31, 2019, 5:36am UTC](https://forum.inductiveautomation.com/t/mobile-application/27031 "2019-07-31T05:36:51Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![tom1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tom1/32/21417_2.png) [@tom1](https://forum.inductiveautomation.com/u/tom1)\ **Post date:** [April 6, 2021, 1:26am UTC](https://forum.inductiveautomation.com/t/mobile-application/27031/2 "2021-04-06T01:26:05Z")
I know this thread is very old but I was just experiencing the same issue. In my case, I am using Nginx as a reverse proxy and managing SSL there. If I bypass Nginx and connect directly to the Ignition gateway, this issue goes away. I had a [similar issue with Designer Launcher](http://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027) however the details here seem to be different. The request that is failing is to `/data/perspective/runnable-projects`. If I make that same request from another client like a browser or curl, the request succeeds through Nginx. From the mobile client (iOS), Nginx responds with a `400` status. It appears that the mobile client is making an unusual request that the Igntion gateway can accept but other servers like Nginx will not. The same `400` response is given to the mobile client when it verifies the hostname and port by requesting `/system/gwinfo` however the mobile client appears to be happy with any response and verifies the address even after receiving a `400` status. In the case of using Nginx, I do not see a way around this. Hopefully one of the product owners can weigh in. --- _[View the full topic](https://forum.inductiveautomation.com/t/mobile-application/27031)._