These codes indicate the reason why a streaming session ended or failed. They help developers and administrators diagnose connection or application issues.Documentation Index
Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt
Use this file to discover all available pages before exploring further.
| Code | Name | Description | Possible Causes |
|---|---|---|---|
| 1000 | Normal Closure | The streaming session ended normally. | User closed the browser, session ended intentionally, or application exited normally. |
| 1001 | Going Away | The client or server closed the connection because it is leaving. | Browser tab closed, page navigation, server restart, or network interruption. |
| 1005 | No Status Received | Connection closed without receiving a status code. | Network disruption, browser crash, or unexpected client disconnect. |
| 1006 | Abnormal Closure | Connection closed unexpectedly without a proper closing handshake. | Network instability, firewall/proxy interference, WebRTC failure, or server crash. |
| 4000 | Project Disabled | The requested project was disabled by admin while it was running. | Project disabled by the owner via dashboard. |
| 4001 | No Worker Node Available | The platform could not find an available worker node to run the application. | All worker nodes are busy, insufficient GPU resources, or worker nodes are offline. |
| 4002 | Application Not Found | The requested application does not exist on the server. | Incorrect project/application ID, deleted application, or deployment incomplete. |
| 4003 | Application Unable to Launch | The server attempted to start the application but failed. | Missing dependencies, incorrect launch configuration, or insufficient GPU/CPU resources. |
| 4004 | Maximum Runtime Reached | The application session exceeded the allowed runtime limit. | Runtime limits configured on the platform or session timeout reached. |
| 4005 | Streamer Not Found | The signaling server could not locate an active streamer instance. | Streamer failed to start, crashed during launch, or worker node failed to register. |
| 4006 | Application Closed / Crashed | The application terminated unexpectedly during the session. | Application crash, runtime error, or system resource exhaustion. |
| 4007 | Reconnection Failed | The client attempted to reconnect to the session but the attempt failed. | Session expired, application instance terminated, or network instability prevented reconnection. |