# Gateway behind reverse proxy not accessible from designer

**URL:** <https://forum.inductiveautomation.com/t/gateway-behind-reverse-proxy-not-accessible-from-designer/69736>\
**Category:** Ignition\
**Tags:** ignition81, docker\
**Created:** [February 12, 2023, 2:29am UTC](https://forum.inductiveautomation.com/t/gateway-behind-reverse-proxy-not-accessible-from-designer/69736 "2023-02-12T02:29:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![theerthraj.munusamy](https://avatars.discourse-cdn.com/v4/letter/t/45deac/32.png) [@theerthraj.munusamy](https://forum.inductiveautomation.com/u/theerthraj.munusamy)\
**Post date:** [February 12, 2023, 2:29am UTC](https://forum.inductiveautomation.com/t/gateway-behind-reverse-proxy-not-accessible-from-designer/69736/1 "2023-02-12T02:29:56Z")

</div>

Hello,

We have deployed a gateway as a container exposed using a nginx reverse proxy.

Nginx proxy is set to server on 443 and Ignition gateway is set to use 8043 port. Both configured with the same SSL certificates. SSL settings are green in Web Server page of gateway config.

Now, we are able to access the gateway via Chrome, however if we try to add the the gateway in designer it says host unreachable.

Has anyone come across this issue. Please let us know.

Thanks.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [February 13, 2023, 4:00pm UTC](https://forum.inductiveautomation.com/t/gateway-behind-reverse-proxy-not-accessible-from-designer/69736/2 "2023-02-13T16:00:47Z")

</div>

Make sure that your reverse proxy configuration is setting headers to facilitate upgrading of websockets connections, e.g.:

```auto
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

```