# Websocket disabled on Proxy

**URL:** <https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 2, 2024, 7:53pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852 "2024-05-02T19:53:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joel\_Villeneuve](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Villeneuve](https://forum.inductiveautomation.com/u/Joel_Villeneuve)\
**Post date:** [May 2, 2024, 7:53pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/1 "2024-05-02T19:53:35Z")

</div>

Hi,

I would like to know if it is possible to not use WebSocket protocol using Ignition Perspective. I have a customer which use our project in Ignition Perspective and its proxy does not allow Websocket connections. The customer asks if we can use another protocol.

Is it possible ?

Thanks,

Joel

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 2, 2024, 7:54pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/2 "2024-05-02T19:54:18Z")

</div>

No, WebSockets are required.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [May 2, 2024, 10:14pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/3 "2024-05-02T22:14:40Z")

</div>

Out of curiosity, what is the reverse proxy they're using, as I thought most of the modern reverse proxies supported WebSockets. I've been sticking with HAProxy, but know that Nginx is also popular, but I've used even some built into firewalls without issues. This would also be good information just to have documented on these forums so everyone else knows what to avoid.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 2, 2024, 10:17pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/4 "2024-05-02T22:17:07Z")

</div>

Yeah I'm curious as well. I feel like it's been 10+ years since most proxies got WebSocket support.

---

<div class="post-metadata">

**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\
**Post date:** [May 2, 2024, 11:06pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/5 "2024-05-02T23:06:56Z")

</div>

Caddy also works.

---

<div class="post-metadata">

**Author:** ![Joel\_Villeneuve](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Villeneuve](https://forum.inductiveautomation.com/u/Joel_Villeneuve)\
**Post date:** [May 3, 2024, 2:14pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/6 "2024-05-03T14:14:15Z")

</div>

I could not tell you, but I think their proxy support Websocket but they block websockets traffic on purpose.

---

<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:** [May 3, 2024, 2:15pm UTC](https://forum.inductiveautomation.com/t/websocket-disabled-on-proxy/89852/7 "2024-05-03T14:15:58Z")

</div>

> [@Joel\_Villeneuve](#):
>
> block websockets traffic on purpose.

They'll have to make an exception for Perspective.