Troubleshooting & Errors

DeskNoria error and symptom reference

A quick lookup table for common DeskNoria errors, statuses and first troubleshooting step.

Applies to DeskNoria 1.5.480 Updated September 21, 2026

Quick reference

Error / symptom First thing to check
Agent offline Agent service/process, Internet/DNS/TLS and current Signaling presence.
Agent.Session v2 unavailable Windows Agent service-to-session broker lifecycle and stale Session process.
WebSocket receive failed Public endpoint, reverse proxy, Signaling restart/failover and reconnect logs.
Waiting for first video Capture source, ICE/media state and codec/decoder startup.
DXGI Desktop Duplication is unavailable... Selected monitor/desktop, GPU/driver state and secure desktop context.
chunk-order mismatch... Admin/Agent File Transfer versions, transport and DNX1 logs.
Unsafe path found in update archive... Package archive layout; regenerate package, do not bypass validation.
Agent offline. Live logs are unavailable. Restore Agent presence before using Live Log Search.
[DeskNoria] This connection was interrupted. Unexpected Terminal transport loss; inspect Signaling/network reconnect.
Chat updates only after Refresh Cross-node Chat event fan-out, Redis and Signaling version alignment.
No Chat notification Confirm the incoming realtime Chat event reaches Admin first.
SFC final result appears but no live output Agent real-time output chunks and admin_command_progress delivery.
Feature disabled/denied License entitlement, Agent assignment and user permission.
Mass Deployment preflight/signature failure Target compatibility and deployment package verification policy.

When escalating

Include the exact error text, DeskNoria version, Agent platform, timestamp, Agent identity, relevant Admin/Agent logs and whether the affected operation was using direct P2P or TURN.

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.