Using long duration mp4 files (up to 3 hours), with jwplayer 6. Some of our customers report getting "Cannot load M3U8: crossdomain access denied" errors sometimes, even if the next time they access the video it seems to be gone.
It may be important to know that in order to share port 80 on a single server, we are using an Apache vhost as local proxy to 1935 so that all HLS requests are proxied locally and served by Apache.
When the error happens, we see this in the apache log:
[Wed Sep 17 18:34:07.700734 2014] [proxy_http:error] [pid 14909] (70014)End of file found: [client 22.214.171.124:57089] AH01102: error reading status line from remote server localhost:1935
[Wed Sep 17 18:34:07.700775 2014] [proxy:error] [pid 14909] [client 126.96.36.199:57089] AH00898: Error reading from remote server returned by /crossdomain.xml
So we thought we'd bypass this by serving the crossdomain.xml locally, and now it is a "Cannot load M3U8: 404 not found" error that jwplayer is showing.
We are suspecting that Wowza is too slow fragmenting the data; is Wowza supposed to block serving the crossdomain.xml file when remuxing a file ? We don't see anything in the wowza error logs, absolutely nothing.
This looks like an interesting and unusual problem. Can you post this to
firstname.lastname@example.org including all the details here and a reference to this forum post. This will generate a ticket for you.
Please also provide the following if possible:
- A ZIP file containing your conf/, logs/, transcoder/ and manager/logs folders. If you are not sure how to get this information please see the following tutorial. Please do make sure you provide logs which show Wowza server starting.
We are experiencing the same issue as the OP (sans the Apache layer). Restarting the WowzaStreamingEngine service seems to temporarily alleviate the issue but we've no idea what the root cause could be.