Error codes
This topic describes common error codes in ApsaraVideo Player SDK for Web. You can query error codes returned when you use ApsaraVideo Player SDK for Web to troubleshoot the errors.
Code | Description |
4001 | The parameter is invalid. |
4002 | The playback credential has expired. When playing with VID PlayAuth or VID STS, check the player initialization parameter authTimeout. This parameter controls the effective duration of the playback address. For more information, see Play on-demand videos. |
4003 | The URL is invalid. |
4004 | The URL does not exist. |
4005 | An error has occurred when the player started to download data. Check the network connectivity and whether the playback URL is accessible. |
4006 | An error has occurred when the player started to download metadata. |
4007 | A playback error has occurred. |
4008 | The loading has timed out. Please check whether the client network and playback address can be accessed normally, and view the specific errors of the on-demand service request in the Network. For details, see Cross-origin error when playing FLV or M3U8 files and Handling DNS resolution failures. |
4009 | A data request error has occurred. Please check whether the client network and playback address can be accessed normally, and view the specific errors of the on-demand service request in the Network. For details, see Cross-origin error when playing FLV or M3U8 files and Handling DNS resolution failures. |
4010 | Videos encrypted using Alibaba Cloud propriety cryptography cannot be played. |
4011 | The video format is not supported. |
4012 | The playauth parameter failed to be parsed. |
4013 | The playback data failed to be decoded. Check whether the browser supports the video format. If the same video is normal at other ends and cannot be played only in iOS Safari, please refer VOD video playback fails on iOS. |
4014 | The network is unavailable. |
4015 | Data retrieving is aborted. |
4016 | Data loading failed due to a network error. |
4017 | The returned playback URL is empty. |
4018 | The Digital Rights Management (DRM) license request failed. |
4019 | Playback is blocked if recording via a browser plugin or playback in a 360 mini-window is detected. Check whether the browser recording plug-in or 360 small window playback is enabled, and try again after closing. |
4020 | General Media Management Service: The data does not exist or has been deleted. |
4021 | The browser does not support DRM. |
4022 | DRM video loading error, such as using a non-HTTPS environment or an incorrect M3U8 format. Note shaka-player is used for playback in DRM WideVine. If DRM-encrypted playback failed, you can query error codes described in this topic. You can also obtain the error details described on the error.js page. |
4023 | The video cannot be played in this region. |
4100 | The RTS signaling request failed. |
4110 | WebRTC is not supported by the RTS browser. |
4111 | RTS is not supported on this browser. |
4112 | (RTS) The browser version is too low. |
4113 | (RTS) The browser does not support H.264. |
4114 | Failed to create an offer for RTS. |
4115 | RTS autoplay failed. |
4116 | (RTS) Incorrect protocol for the playback URL. |
4118 | The specified HTML element is not an audio or a video stream. |
4121 | The RTS HTTP request failed. |
4122 | The RTS response failed. |
4200 | The RTS playback failed error occurs when a data retrieval operation exceeds the timeout specified by rtsLoadDataTimeout. |
4300 | wasm/worker/canvas/audiocontent/webgl is not supported and H.265 videos cannot be played. |
4304 | An unknown container format was encountered during H.265 parsing. |
4400 | An unknown error has occurred. Resources failed to be loaded due to a server or network error, or the resource format is not supported. |
4500 | A server request failed. View the specific error message of the VOD request. |