Infrastructure & Signaling

Signaling Server overview

What DeskNoria Signaling does and what it deliberately does not carry.

Applies to DeskNoria 1.5.480 Updated September 21, 2026

Responsibilities

The Signaling Server handles authenticated WebSocket/HTTP control traffic, session negotiation, presence, account-driven events, task/chat routing and other orchestration.

Media boundary

Remote Desktop video and File Transfer payloads are not sent through the Signaling server. The server coordinates WebRTC/ICE and can provide TURN configuration, but the payload follows the negotiated peer/relay route.

Database

MariaDB stores durable state. Schema migration is checked before the listener becomes available so an incompatible schema does not silently run as healthy.

Reverse proxy

A typical production deployment listens on loopback and relies on the existing HTTPS reverse proxy for public HTTP/WebSocket access.

Need more help? Collect the relevant DeskNoria Admin/Agent logs and the exact visible error text before troubleshooting. For connection problems, include whether the affected Agent is Windows or Linux and whether the session used P2P or TURN.

Related articles

Active-active Signaling clusterHow multiple DeskNoria Signaling nodes coordinate sessions and account events. Rolling upgrade of Signaling nodesUpgrade an active-active DeskNoria Signaling deployment without stopping every node at once. STUN, TURN and relay behaviorHow TURN fits into DeskNoria Remote Desktop and File Transfer connectivity. Mass DeploymentDeploy MSI, EXE and Linux packages to multiple managed Agents with per-target tracking.