Pusher SDK
Pusher clients are fully compatible with the WebSocket protocol implemented by soketi, which means you can easily take advantage of amazing features like private channels, presence channels, and client events. You simply need to point the Pusher compatible client to the soketi server address:
const PusherJS = require('pusher-js');
​
let client = new PusherJS('app-key', {
wsHost: '127.0.0.1',
wsPort: 6001,
forceTLS: false,
encrypted: true,
disableStats: true,
enabledTransports: ['ws', 'wss'],
});
​
client.subscribe('chat-room').bind('message', (message) => {
alert(`${message.sender} says: ${message.content}`);
});
Make sure that enabledTransports is set to ['ws', 'wss']. If not set, in case of connection failure, the client will try other transports such as XHR polling, which soketi doesn't support.

SSL Configuration

When running the server in SSL mode, you may consider setting the forceTLS client option to true. When this option is set to true, the client will connect to the wss protocol instead of ws:
const PusherJS = require('pusher-js');
​
let client = new PusherJS('app-key', {
...
wssHost: '127.0.0.1',
wssPort: 6001,
forceTLS: true,
enabledTransports: ['wss'],
...
});

Encrypted Private Channels

​Pusher Encrypted Private Channels are also supported, meaning that for private channels, you can encrypt your data symmetrically at both your client and backend applications, soketi NOT knowing at all what the actual data is set, acting just like a deliverer.
const PusherJS = require('pusher-js');
​
let client = new PusherJS('app-key', {
...
encryptionMasterKeyBase64: "YOUR_MASTER_KEY", // generate this with, e.g. 'openssl rand -base64 32'
...
});
​
client.subscribe('private-encrypted-top-secret-room').bind('message', (message) => {
// The message is unknown to soketi
});
Copy link
On this page
SSL Configuration
Encrypted Private Channels