Infrastructure & Signaling

Active-active Signaling cluster

How multiple DeskNoria Signaling nodes coordinate sessions and account events.

Applies to DeskNoria 1.5.480 Updated September 21, 2026

Node identity

Each Signaling node registers a stable node identity/role and publishes health/presence information.

Redis control plane

Redis carries ephemeral cross-node routing/presence events. It is not used for Remote Desktop media or File Transfer payload data.

Cross-node routing

Session-control and account events can be forwarded to the node that owns the relevant live WebSocket/Agent presence. Chat events are fanned out across live nodes so notifications and receipts remain realtime when the HTTP request and Admin WebSocket land on different nodes.

Failover

Agent ownership uses generation/ownership fencing so a stale socket from an old node cannot incorrectly mark a newly reconnected Agent offline.

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

Signaling Server overviewWhat DeskNoria Signaling does and what it deliberately does not carry. 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.