There are five error groups:
- general player errors
- stream errors
- media element errors
- network connection errors
- setup errors
Following some of the most frequent errors will be described.
To see all errors please have a look at the possible
These errors have codes in a range from 1000 to 1999.
1xxx codes represent general errors of the player on startup or playback.
The most frequent errors here are
1005 Playback must be initialized by user gesture.
This is related to autoplay. It is recommended to review the autoplay settings.
Please have a look at our blog entry about autoplay policies.
1007 Playback suspended by external reason.
This is indicating a special condition on mobile devices when the playback has been stopped by an event in the browser or system on a mobile device.
NOTE: This is a non critical error.
- Player tab going to background after a tab switch
- Browser application being minimized or closed
- Browser application being interrupted by the system, e.g. in case of an incoming call or device being locked
1009 Playback failed because the player was in visibility state 'hidden' at load start.
This is related to a policy in some browsers, e.g. Chrome, Chromium based and Safari preventing media playback start in a background tab, a tab that did not have focus/visibility yet.
These errors have codes in a range from 2000 to 2999.
2xxx codes are related to fetching the media stream on the player side and the occurrence
of timeouts during loading or playback. It is about the availability of the stream on the player side,
which can be connected to the general availabilty of the stream, but as well to bad network conditions
on the player side.
The most frequent errors here are
2001 The requested stream can not be found.
No stream info and media data received.
2002 No media available.
The stream was already playing, but media data stopped receiving.
2003 Not enough media data received.
Stream info is received, but no media data was fetched.
2004 The source stream has been stopped.
The stream was already playing, but the stream was unpublished.
These errors have codes in a range from 3000 to 3999.
3xxx codes are related to media playback errors in the system/browser playback components,
MediaElement and/or Media Source Extensions.
The most present errors here are
3003 An error occurred when decoding media.
An receiving media data chunk couldn't be decoded.
3100 The media source extension changed the state to 'ended'.
The MSE stopped working.
These errors have codes in a range from 4000 to 4999.
4xxx codes are related to network errors of the media stream connections. Connect failures can be caused by bad network conditions, firewall issues and in rare cases by overreacting ad blockers.
4001 Could not open connection. Timeout reached.
The websocket server is not available or not present, a timeout for establishing the connection is reached.
4006 The source request was aborted by timeout.
These errors have codes in a range from 5000 to 5999.
5xxx are related to errors during the setup/configuration stage, mainly configuration errors and insufficient browser capabilities. In most cases it makes sense to check the configuration that has been used.
onVolumeChange) during setup.
- "undefined is not an object"
5002 This browser does not fully support HTML5 and H5Live.
The used browser does not fully support HTML5 and H5Live.
Supported browsers are:
- Chrome >=54 (Windows, MacOSX, Android)
- Firefox >=48 (Windows, MacOSX, Android)
- Microsoft Edge (Windows)
- Microsoft Internet Explorer 11 (at least Windows 8)
- Safari (MacOSX & at least iOS 10)