# Limit the remote access to desinger & gateway config page

**URL:** <https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178>\
**Category:** Ignition\
**Created:** [October 30, 2020, 6:05pm UTC](https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178 "2020-10-30T18:05:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [October 30, 2020, 6:05pm UTC](https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178/1 "2020-10-30T18:05:39Z")

</div>

Hi,  
When we open port 8088 or 443 to get remote access perspective web pages we also make possible remote access to the designer and gateway config pages. So if some one can get password he can easily go to config page and change all security setting.

I believe if we have separate port for desinger and gateway from perspective port it is much safer for remote access applications.  
We can drop any access to that port with firewall and even user and password are compremised at least with using security zone(that limit all outside IP) the hacker can’t send any command.

---

<div class="post-metadata">

**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:** [October 31, 2020, 12:40pm UTC](https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178/2 "2020-10-31T12:40:49Z")

</div>

Please don’t. If you really need this, use a load balancer/proxy to forward only the parts of the hierarchy you wish to permit to outsiders.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [October 31, 2020, 7:35pm UTC](https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178/3 "2020-10-31T19:35:57Z")

</div>

Ok but when every things are in port 443 or 8088 how proxy can differentiate them?

---

<div class="post-metadata">

**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:** [November 1, 2020, 7:28pm UTC](https://forum.inductiveautomation.com/t/limit-the-remote-access-to-desinger-gateway-config-page/40178/4 "2020-11-01T19:28:02Z")

</div>

Load balancers and reverse proxies can look at the path of a URL to decide how/if to proxy.
