# Public Facing HTTPS, but local HTTP, to Gateway **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [February 19, 2024, 4:20pm UTC](https://forum.inductiveautomation.com/t/public-facing-https-but-local-http-to-gateway/85951 "2024-02-19T16:20:54Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Tim.Johnson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim.johnson/32/10597_2.png) [@Tim.Johnson](https://forum.inductiveautomation.com/u/Tim.Johnson)\ **Post date:** [February 19, 2024, 4:20pm UTC](https://forum.inductiveautomation.com/t/public-facing-https-but-local-http-to-gateway/85951/1 "2024-02-19T16:20:54Z")
We have a public-facing gateway, with all traffic forced to https. That's not a problem, and I don't have any reason to change it. However, the issue is when a developer is connected locally (via VPN, not using the Fully Qualified Domain Name, but rather an IP address) because, although we have a valid cert, when we try to select the 'Trust Certificate' button, it says 'Certificate Invalid'. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/f/3facfc7e4152bfcc016863ed8fea646d073cc1c5.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/8/481812db361419063b9fc4ce5ebb7a85e9d37e74.png) Although we can successfully open a Designer session using the FQDN... ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5f6db110bd5f0a009d67835246799d26e8ad5e78.png) and we can see all the projects and files in the tree (views, styles, etc), when we try to open any, we get a '_Not Accessible_' error. Is there a way we can either enable http access ONLY from the local network, or be able to trust the cert? (Oh, and before you give me grief about showing our domain and ip addresses, they're not real ...obviously. I've changed them for display.) ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [February 19, 2024, 4:42pm UTC](https://forum.inductiveautomation.com/t/public-facing-https-but-local-http-to-gateway/85951/2 "2024-02-19T16:42:03Z")
I've been able to do what you want by ensuring that "Force Secure Redirect" was disabled in the Ignition web server settings, and having our public-facing web proxy in front of it (e.g. nginx, AWS load balancer, whatever) enforce the HTTPS redirect there. Then, I had to tunnel or VPN into the network containing the gateway and I could still access it as `http://10.10.10.10:8088` just fine. Is the setup I described not possible with your network architecture? ---
**Author:** ![Tim.Johnson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim.johnson/32/10597_2.png) [@Tim.Johnson](https://forum.inductiveautomation.com/u/Tim.Johnson)\ **Post date:** [February 19, 2024, 4:47pm UTC](https://forum.inductiveautomation.com/t/public-facing-https-but-local-http-to-gateway/85951/3 "2024-02-19T16:47:44Z")
Thanks @justin.brzozoski, I'll have to check, but I think it might be. That's what I wondered. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 19, 2024, 5:07pm UTC](https://forum.inductiveautomation.com/t/public-facing-https-but-local-http-to-gateway/85951/4 "2024-02-19T17:07:15Z")
If you go that route, you will want to tell Ignition to trust the forwarded-for headers from nginx (or other proxy).