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.
Error code | Description |
4001 | The parameter is invalid. |
4002 | The playback credential has expired. |
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. Check the network connectivity and whether the playback URL is accessible. |
4009 | A data request error has occurred. Check the network connectivity and whether the playback URL is accessible. |
4010 | Videos encrypted by 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. |
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 failed to be obtained. |
4019 | A browser plug-in is used for recording or a video is played in the picture-in-picture (PiP) mode. |
4020 | The data does not exist or is deleted when you use General Media Management Service to play videos. |
4021 | The browser does not support DRM. |
4022 | The DRM video failed to be loaded. This error may occur if you do not use HTTPS or the M3U8 format is incorrect. 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 message failed to be obtained. This error may occur only when the signaling request over Real-Time Streaming (RTS) failed. |
4110 | The browser does not support WebRTC. This error may occur only when you play a video over RTS. |
4111 | The browser is not supported. This error may occur only when you play a video over RTS. |
4112 | The version of the browser is outdated. This error may occur only when you play a video over RTS. |
4113 | The browser does not support H.264 videos. This error may occur only when you play a video over RTS. |
4114 | The create offer operation failed. This error may occur only when you play a video over RTS. |
4115 | The autoplay failed. This error may occur only when you play a video over RTS. |
4116 | The protocol of the playback URL is incorrect. This error may occur only when you play a video over RTS. |
4118 | The specified HTML element is not an audio or a video stream. |
4121 | The HTTP request failed. This error may occur only when you play a video over RTS. |
4122 | The answer command failed to be run. This error may occur only when you play a video over (RTS. |
4200 | The playback failed. This error may occur only when you play a video over RTS. |
4300 | wasm/worker/canvas/audiocontent/webgl is not supported and H.265 videos cannot be played. |
4304 | An unknown container format is used during the parsing of H.265 videos. |
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. |