Bitmovin WordPress Plugin

FAQ

Why does the player show the error message “Your player is not allowed to play on the domain evil.com”?

The player contacts our licensing server to detect if it is allowed to play on the current domain.
Browser extensions, like Allow-Control-Allow-Origin: * allows CORS requests without honoring CORS headers from the server, but in return changes the origin from the actual domain to evil.com.
Please disable/remove such extensions and the player should work as expected.

I get the error message “1002: Key or domain is invalid”

The error is shown, because either the key you entered in the configuration is incorrect or
if you are using the URL you entered during the checkout process, is not valid or incorrect.
Non-valid URLs can for instance be caused by incorrect sub-domains, the URL you provided does not fully match the URL of the deployment,
or you entered an IP address instead of the domain name.

I setup the Bitmovin player, but no video element is shown”

This can have different reasons.
Please open the console of your web browser (e.g. by pressing F12 in Google Chrome or Mozilla Firefox),
which provides information in more detail on possible errors.

Why do I see error messages in my browser’s console?

The error messages as shown in the image below may appear in a browser’s console.
This is not a bitmovin player error, but the errors are thrown from Google’s ChromeCast SDK if the Cast extensions can’t be found.
Unfortunately, there is currently no way to prevent these errors from happening or from showing up in the console, as explained by the developers in the related Google Cast SDK issue.
These errors do not prevent your website or the bitmovin player from working as expected. ChromeCast errors in browser’s console This affects pro and enterprise edition only..

Why are the colors of my video not the same in different browsers?

The bitmovin player relies on the browser’s capabilities to decode and render the video.
This has the advantage to be able to use hardware decoding which is much faster and also better for battery life / energy consumption than software decoding.
But different browsers may use different encoders with different settings.
This difference is especially visible between HTML5 and FLASH videos.
So unfortunately we can not change this behaviour.

The player is not loading segments, altough the MPD is correct?

If the player is not loading segments which lies on another server,
make sure CORS (for the HTML5 player) is enabled a crossdomain.xml
(for the Flash based version of bitdash) is placed on the server containing the element.