How to Set Up a Private Self-Hosted WebRTC Signaling Server for Remote Support

Why internal enterprise networks need dedicated signaling

For organizations operating under strict compliance frameworks (such as healthcare, banking, and government IT), sending session handshake tokens to external public signaling servers is often restricted by network security policies.

Because Remote Desk P2P (Redesk) is built with open standards, IT administrators can host their own private signaling server on an internal LAN or isolated private cloud instance in less than five minutes.

Deploying the lightweight Node.js signaling daemon

The signaling server requires only Node.js and the native ws library. It acts as an in-memory session router without needing an external database:

// server.js
const { WebSocketServer } = require('ws');
const wss = new WebSocketServer({ port: 5000 });
const sessions = new Map();

wss.on('connection', (ws) => {
  ws.on('message', (message) => {
    const data = JSON.parse(message);
    if (data.type === 'register') {
      sessions.set(data.code, ws);
    } else if (data.type === 'relay') {
      const peer = sessions.get(data.targetCode);
      if (peer && peer.readyState === ws.OPEN) peer.send(message);
    }
  });
});
console.log('Private WebRTC Signaling active on port 5000');

Configuring the Redesk desktop client

1. In Remote Desk P2P, navigate to Settings → Network.
2. Toggle Custom Signaling Server on.
3. Enter your private WebSocket URL (e.g. wss://support.internal.yourcompany.com/signaling).
4. Click Save. All subsequent remote sessions will negotiate peer connections exclusively through your private server.