Troubleshooting
Video streaming HTTP status codes
The following table includes all possible HTTP status codes returned when requesting videos and live streams for manifests (e.g., .m3u8 and .mpd) or chunks (e.g., .ts, .mp4, etc.).
Code | Status | Description |
---|---|---|
200 | OK | All OK |
403 | Forbidden | Access is denied. If you use any distribution restriction, such as geo-restriction or token, you must satisfy this condition for access. |
404 | Not Found | |
There is no video, or the live stream is temporarily not delivering chunks. Check the request link or activate your video. For Live streams in CMAF format, you can check the extra header “X-Err-Code”:
| ||
422 | Unprocessable Content | This is advanced functionality (e.g., custom encoding presets). To enable it, contact your manager or the support team. |
500 | Internal Server Error | An unexpected issue happened on the server. This may be a local error in a specific video. In this case, check the video processing status in your account. If the error is global, the information will be on the status page. |
502 | Bad Gateway | An unexpected issue happened on the server. This may happen when VOD or Live can’t be delivered over CDN because an incorrect response was received from an origin (storage or live transcoder). In this case, check the video processing status or live stream transcoding in your account. If the error is global, the information will appear on the status page. |
503 | Service Unavailable | An unexpected issue happened on the server. This may be a local error in a specific video. In this case, check the video processing status in your account. If the error is global, the information will be on the status page. |
504 | Gateway Time-out | Timeout for receiving data from the source. Try checking the status of video sending/ingesting and transcoding. |
The system health status page is available at https://status.gcore.com/