# Max connections for WebSocket SSL termination

**URL:** <https://www.ruby-forum.com/t/max-connections-for-websocket-ssl-termination/236040>\
**Category:** NGINX\
**Created:** [August 1, 2013, 9:54am UTC](https://www.ruby-forum.com/t/max-connections-for-websocket-ssl-termination/236040 "2013-08-01T09:54:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [August 1, 2013, 9:54am UTC](https://www.ruby-forum.com/t/max-connections-for-websocket-ssl-termination/236040/1 "2013-08-01T09:54:14Z")

</div>

Hey guys,

I have been using nginx in my personal life for a couple of years,  
recently  
dropping totally apache and I must admit that this software rocks.  
Congrats  
to all the devs for the fantastic job in the new-event-driven-world.

Secondly, at work, we are trying to use nginx as a SSL endpoint for our  
websocket connections. We need to handle handred of thousands of  
permanent  
connections, and given the problem that Node.js (our backend) has with  
SSL  
(leaks memory in combination with websockets), we decided to give nginx  
a  
try.

Problem? We can only handle 64k connections due to the limit of actual  
ports  
on a unix machine. I think this cannot be workarounded with nginx  
configurations, right?

We can switch to listen to a unix socket (so Node.js is not serving in a  
http port, but on a unix socket), which _I think_ that could resolve the  
problem.

Thanks for your help.

Posted at Nginx Forum:

> **[Max connections for WebSocket SSL termination](https://forum.nginx.org/read.php?2,241442,241442#msg-241442)**
>
> Hey guys, I have been using nginx in my personal life for a couple of years, recently dropping totally apache and I must admit that this software rocks. Congrats to all the devs for the fantastic job in the new-event-driven-world. Secondly, at work,...