Types of errors
There are five main types of errors which are briefly described in this section. You can click on the error type to see the specific errors for each type, if applicable.
- Standard errors dispatched from the Errors Plugin: These error names start with MEDIA_ERR.
- Custom errors defined by Brightcove and dispatched from the Errors Plugin: These error names start with PLAYER_ERR.
- Errors dispatched from the Video Cloud catalog: These error names start with VIDEO_CLOUD_ERR. Of course, Brightcove Player customers will never see these errors.
- Errors reported in the browser Development Tools Console: These errors are developer oriented as they will only be see in a browser's Console.
- Custom errors that are user defined and dispatched by the Errors Plugin: These error names are defined by by the user, for example AGE_GATE_ERROR.
For complete details see the Standard errors section of the Display Error Messages Plugin document.
|1||MEDIA_ERR_ABORTED||The video download was canceled||You aborted the media playback.|
|2||MEDIA_ERR_NETWORK||The video connection was lost, please confirm you're connected to the Internet||A network error caused the media download to fail part-way.|
|3||MEDIA_ERR_DECODE||The video is bad or in a format that can't be played on your browser||The media playback was aborted due to a corruption problem or because the media used features your browser did not support.|
|4||MEDIA_ERR_SRC_NOT_SUPPORTED||This video is either unavailable or not supported in this browser||The media could not be loaded, either because the server or network failed or because the format is not supported.|
|5||MEDIA_ERR_ENCRYPTED||The video you're trying to watch is encrypted and we don't know how to decrypt it||The video you're trying to watch is encrypted and we don't know how to decrypt it.|
|Unknown||MEDIA_ERR_UNKNOWN||N/A||An unanticipated problem was encountered, check back soon and try again.|
Custom Brightcove errors
For complete details see the Custom errors section of the Display Error Messages Plugin document.
|-1||PLAYER_ERR_NO_SRC||No video has been loaded.|
|-2||PLAYER_ERR_TIMEOUT||Could not download the video.|
|Not Set||PLAYER_ERR_DOMAIN_RESTRICTED||This video is restricted from playing on your current domain.|
|Not Set||PLAYER_ERR_IP_RESTRICTED||This video is restricted at your current IP address.|
|Not Set||PLAYER_ERR_GEO_RESTRICTED||This video is restricted from playing in your current geographic region.|
For complete details see the Catalog errors section of the Player Catalog document.
|VIDEO_CLOUD_ERR_ACCOUNT_NOT_FOUND||The player has been configured with an invalid Video Cloud account ID.|
|VIDEO_CLOUD_ERR_RESOURCE_NOT_FOUND||The default playlist ID is invalid.|
|VIDEO_CLOUD_ERR_VIDEO_NOT_FOUND||The default video is invalid.|
|VIDEO_CLOUD_ERR_NOT_PLAYABLE||The Video Cloud video is not playable.|
These errors would appear in a console looking something like this:
|VIDEOJS: ERROR: videojs-contrib-ads has not seen a loadstart event 5 seconds after being initialized, but a source is present. This indicates that videojs-contrib-ads was initialized too late. It must be initialized immediately after video.js in the same tick. As a result, some ads will not play and some media events will be incorrect. For more information, see https://github.com/videojs/videojs-contrib-ads#important-note-about-initialization||You see this because for the IMA3 plugin to function properly it needs to be loaded right after player initialization, before any other plugins are initialized. See the Implement using code section of the IMA3 Plugin doc for the solution.|
Custom user errors
For complete details see the Adding custom errors section of the Display Error Messages Plugin document. There are no standard custom user errors.