# Firewall Ports for Perspective and Vision

**URL:** <https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994>\
**Category:** Ignition\
**Created:** [November 15, 2019, 1:36pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994 "2019-11-15T13:36:34Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![michal.koblasa](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@michal.koblasa](https://forum.inductiveautomation.com/u/michal.koblasa)\
**Post date:** [November 15, 2019, 1:36pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/1 "2019-11-15T13:36:34Z")

</div>

Hello,  
our ignition is behind firewall.  
We allowed our Gateway port: 8080, but Perspective application is not running.  
It gets stuck on request: 101 Switching Protocol.

What ports we need to allow in our firewall?

 ![Obr%C3%A1zek%2014](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/01811594c9be306a73e86b79b1bb777d1a0c7bcd.png)

---

<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:** [November 15, 2019, 1:50pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/2 "2019-11-15T13:50:14Z")

</div>

I don’t think you need an additional port unblocked. It looks like the firewall may be blocking the websocket upgrade request.

---

<div class="post-metadata">

**Author:** ![michal.koblasa](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@michal.koblasa](https://forum.inductiveautomation.com/u/michal.koblasa)\
**Post date:** [November 15, 2019, 1:54pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/3 "2019-11-15T13:54:30Z")

</div>

Firewall is set to allow communication to Gateway:8080, i think, that our firewall does not care about HTTP request type. It checks just IP+Port (but I´m not completely sure).

My concern is, that websocket is trying to switch port of communication, I´m not sure.

---

<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:** [November 15, 2019, 2:02pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/4 "2019-11-15T14:02:30Z")

</div>

WebSocket upgrades happen in place, on the existing connection. It’s just a protocol switch.

---

<div class="post-metadata">

**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\
**Post date:** [November 16, 2019, 4:28am UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/5 "2019-11-16T04:28:48Z")

</div>

What do Ignition clients ( **vision** and **perspective** ) use for communiction with server, **websockets** or **HTTP**? Just for clarification. I thought they use **HTTP(S).**

---

<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:** [November 16, 2019, 12:54pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/6 "2019-11-16T12:54:31Z")

</div>

Vision uses HTTP(S), Perspective uses both HTTP(S) and WebSockets.

---

<div class="post-metadata">

**Author:** ![PRAMANJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pramanj/32/66935_2.png) [@PRAMANJ](https://forum.inductiveautomation.com/u/PRAMANJ)\
**Post date:** [November 16, 2019, 1:22pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/7 "2019-11-16T13:22:09Z")

</div>

Thanks a lot Kevin . Have a nice weekend .

---

<div class="post-metadata">

**Author:** ![michal.koblasa](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@michal.koblasa](https://forum.inductiveautomation.com/u/michal.koblasa)\
**Post date:** [November 18, 2019, 8:08am UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/8 "2019-11-18T08:08:52Z")

</div>

Hello Guys,  
i did some of testing and i found, that firewall is ok.  
But Chrome settings is not much confortable with different port: 8080.

Based on docs it seems i may need to use SSL port or somehow setup proxy, but I´m not sure error is weird, because other devices with Chrome are running well (through same firewall).

Found in docs for websocket:

> **Warning:** The server may listen on any port it chooses, but if it chooses any port other than 80 or 443, it may have problems with firewalls and/or proxies. Browsers generally require a secure connection for WebSockets, although they may offer an exception for local devices.

Copied out of here:

> **[Writing WebSocket servers - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_servers)**
>
> A WebSocket server is nothing more than an application listening on any port of a TCP server that follows a specific protocol. The task of creating a custom server tends to scare people; however, it can be straightforward to implement a simple...

---

<div class="post-metadata">

**Author:** ![andytimc](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andytimc/32/11938_2.png) [@andytimc](https://forum.inductiveautomation.com/u/andytimc)\
**Post date:** [February 21, 2020, 2:46pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/9 "2020-02-21T14:46:53Z")

</div>

Is it possible to make ignition and vision run on different ports, for example Vision on 8088 and perspective on 8089? My company wants to go to perspective exclusively because it can work with DUO and other identity providers, but we will lose some vision functionality, so if I can make them run on different ports we can lock down security in other ways.

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [February 21, 2020, 2:59pm UTC](https://forum.inductiveautomation.com/t/firewall-ports-for-perspective-and-vision/29994/10 "2020-02-21T14:59:57Z")

</div>

You would probably have to have them running on separate gateways. At least based on the knowledge that I have.
