Hello,
We have configured a Chromecast styled receiver for Kaltura. When I try to play a live stream, I get the following error:
Unsafe attempt to load URL https://dev.yyyyy.com/p/102/sp/10200/playManifest/entryId/0_f4wphewh/format/applehttp/protocol/https/uiConfId/23448172/a.m3u8?referrer=aHR0cHM6Ly9kZXYuY2xvdWR2aWRlby5jb20uY28=&playSessionId=eca13709-002a-256e-b1b2-dd83510aa455 from frame with URL https://www.gstatic.com/cast/sdk/default_receiver/1.0/app.html?skin . Domains, protocols and ports must match
Chromecast is not able to load the Manifest but it works when playing VOD.
Does anyone have any experience fixing these CORS Chrome errors ? Any help will be appreciated.
We are using the latest player (v2.80) and nginx live stream instead of wowza
Thank you,
David
jess
February 11, 2020, 12:54pm
2
Thank you Jess !
We’l check it out.
Regards,
David
Hello Jess,
After going through the documentation, I noticed that I was making a big mistake and using the wrong Chromecast receiver.
I registered a custom receiver pointing to my players plugin (https://dev.yyy.com//html5/html5lib/v2.80/modules/Chromecast/resources/receiver/receiver.html ) and now the player loads consistently for Live and VOD.
The problem now is that I have a different delivery profile domain name (cdn.yyy.com ) from the api/kaltura domain name (dev.yyy.com ) and I’m getting the nasty CORS error that blocks the manifests.
Unsafe attempt to load URL https://cdn.yyy.com/live01/live.m3u8 from frame with URL https://dev.yyy.com/html5/html5lib/v2.80/modules/Chromecast/resources/receiver/receiver.html . Domains, protocols and ports must match.
We have checked and all CORS headers are present.
Since it looks quite normal to have a different delivery domain from kaltura’s api/main domain, is there a simple fix that problem on the player’s module ?
Thank you again for your help,
David