What Ports Do I Need To Open In My Firewall To Allow Channels To Connect?

Client Libraries

WebSocket connections generally work even if a proxy or firewall is in place. This is because they use ports 80 and 443 which are also used by HTTP connections.

In some situations WebSocket connections are blocked over port 80. In this case a secure SSL connection using WSS over port 443 should successfully connect. If this is not the case please contact Pusher support.

By default, the destinations and ports used by Channels clients are as follows:

ws://ws.pusherapp.com on port 80 wss://ws.pusherapp.com on port 443

When a cluster is specified then the destinations and ports used by Channels clients are as follows:

ws://ws-[your-cluster].pusher.com on port 80 wss://ws-[your-cluster].pusher.com on port 443

If pusher-js is used and a fallback transport is used (such as xhr_streaming), the default destinations and ports used by Channels clients are as follows:

http://sockjs.pusherapp.com on port 80 https://sockjs.pusherapp.com on port 443

If you have specified a cluster then the destinations and ports used bu Channels clients are as follows:

http://sockjs-[your-cluster].pusher.com on port 80 https://sockjs-[your-cluster].pusher.com on port 443

If making use of the CDN then the following are used:

js.pusher.com on port 80 js.pusher.com on port 443

Server Libraries

For the server libraries, by default you will need:

api.pusherapp.com on port 80 api.pusherapp.com on port 443

Although, if you have specified a cluster then you will require:

api-[your-cluster].pusher.com on port 80 api-[your-cluster].pusher.com on port 443

Finally, our optional stats collection endpoint requires:

stats.pusher.com port 80 stats.pusher.com port 443

Still have questions? Please reach out to our Support team by visiting this page.