# Corporate firewalls blocking port 8080 for Erizo

**URL:** <https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365>\
**Category:** Support\
**Created:** [January 18, 2017, 10:30pm UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365 "2017-01-18T22:30:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rohit\_Aggarwal](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@Rohit\_Aggarwal](https://discourse.lynckia.com/u/Rohit_Aggarwal)\
**Post date:** [January 18, 2017, 10:30pm UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365/1 "2017-01-18T22:30:25Z")

</div>

Hi, we are facing the issue that many corporate firewalls are blocking port 8080 for Erizo. Our site is completely on https and Chrome throws no error. Corporate firewalls do not block our site but they block Erizo request to port 8080.

Do you have any suggestion on this? I will greatly appreciate your suggestions.

Thanks!  
Rohit

---

<div class="post-metadata">

**Author:** ![Javier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/javier/32/20_2.png) [@Javier](https://discourse.lynckia.com/u/Javier)\
**Post date:** [January 18, 2017, 11:24pm UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365/2 "2017-01-18T23:24:36Z")

</div>

Erizo Controller uses port 8080 for WebSockets. There are two possibilities: the firewalls are blocking access to port 8080 (solution: you can listen on port 443 or deploy a https proxy that forwards connections from 443 to 8080), or they are blocking websockets (your should configure the firewall to accept them).

---

<div class="post-metadata">

**Author:** ![Rohit\_Aggarwal](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@Rohit\_Aggarwal](https://discourse.lynckia.com/u/Rohit_Aggarwal)\
**Post date:** [January 19, 2017, 4:04am UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365/3 "2017-01-19T04:04:50Z")

</div>

Thank you Javier.

Would listening on port 443 require handling CORS? Do you know where I can do CORS setting in Licode? I’m trying to follow this: [Stackoverflow post](http://www.google.com/url?q=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F14003332%2Faccess-control-allow-origin-wildcard-subdomains-ports-and-protocols&sa=D&sntz=1&usg=AFQjCNFpnjoO7Vt0pk1-fUD_5fc9ZfpkJQ) but finding it hard to do this CORS setting in Licode.

I will greatly appreciate your suggestions.

---

<div class="post-metadata">

**Author:** ![Prakhar\_Singh](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/prakhar_singh/32/36_2.png) [@Prakhar\_Singh](https://discourse.lynckia.com/u/Prakhar_Singh)\
**Post date:** [January 21, 2017, 10:16am UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365/4 "2017-01-21T10:16:18Z")

</div>

I am using Nginx for proxying request from 443 to 8080 and it responds with error 502 Bad Gateway for 443 while replies in 200 if requested on port 8080.

---

<div class="post-metadata">

**Author:** ![Rohit\_Aggarwal](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@Rohit\_Aggarwal](https://discourse.lynckia.com/u/Rohit_Aggarwal)\
**Post date:** [January 29, 2017, 5:59pm UTC](https://discourse.lynckia.com/t/corporate-firewalls-blocking-port-8080-for-erizo/365/5 "2017-01-29T17:59:11Z")

</div>

As it turned out, Licode was only listening to IPv6 and not IPv4 for 443. Making it listen IPv4 fixed the problem.