Use a custom domain in FastPix player to brand video playback, boost trust, and control domain routing.
You can use custom domains to stream video assets from a domain of your choice rather than the default fastpix.io. This guide will help you set up and use a custom domain with the FastPix player, enhancing your control over media delivery. Leveraging custom domains can enhance your branding, improve SEO, and increase user trust.
By default, all FastPix video assets—including posters, storyboards, and media sources—are hosted on fastpix.io. This means that when you use the FastPix player without a custom domain, your video and image assets are streamed directly from FastPix servers.
To set up a custom domain with the FastPix player, follow these steps:
media.example.com should point to assets.fastpix.io image.media.example.com should point to images.fastpix.comstream.media.example.com should point to videos.fastpix.io Once your custom domain is set up, the next step is to inform the FastPix player about it using the custom-domain attribute or the customDomain property.
HTML element example
To use a custom domain with the FastPix player in an HTML element, include the custom-domain attribute with your domain:
In this example, media.example.com is your custom domain. Internally, the FastPix player will expand this value to image.media.example.com for images and stream.media.example.com for video streaming.
Here’s a more detailed example of how to integrate the FastPix player with a custom domain:
When you specify a custom domain, the behavior is as follows:
stream.<your-custom-domain>.image.<your-custom-domain>.For example, if your custom domain is media.example.com:
stream.media.example.com.image.media.example.com.If you run into issues while setting up or using a custom domain with the FastPix player, consider these troubleshooting tips:
Check your DNS configuration: Ensure your DNS records are correctly configured and fully propagated.
Inspect network requests: Use your browser’s developer tools to inspect network requests and confirm that assets are being loaded from the correct custom domain.
Review console logs: Look for any errors or warnings in the browser console that could point to configuration issues.