My website http://goproheroes.com works fine in Firefox and Safari, but refuses to play recently in Chrome.
I see tons of XHR requests and no errors, the YT player just refuses to play, no console errors. I can't figure out why.
I've seen this before, and in the other cases it was fixed by adding http:// or https:// in the src in front of your embed url.
Yours is currently src="//www.youtube.com/embed/zvAgYeHAoic"
Related
Any website that embeds a You Tube live stream give me an error message (see below) "This Live Event No Longer Available" in Chrome, only if I'm signed into Chrome. If I sign out of Chrome, or go incognito, the same embedded livestream plays fine. I have reloaded Chrome, deleted all cookies, no help.
I have the same issue and so far signing out of youtube/chrome/gmail or to go incognito is the only solution.
I was trying to load this simple video in firefox but when I try to access the video it loads forever and never plays whereas it works perfectly in chrome. It does the exact same thing with every videos I tried. I don't understand why it does not work.
https://www.w3schools.com/html/mov_bbb.mp4
This is how it looks when I try to open it
It is working in firefox, I think you need to update your browser. Check more for documentation on firefox they have details about it.
I am using videojs to use HLS in Chrome but for a particular URL this fails (CORS issue) but in Safari it plays without problems.
I have a code in videojs but for figure out the problem faster, I used you this online player:
https://videojs.github.io/videojs-contrib-hls/
For this file, problem is present in Chrome (but not in Safari):
https://s3-us-west-2.amazonaws.com/andy-mediaconvert-tests/Haystack.tv/2019-05-10_Output/02_qvbr_ch1/ch1_hd720.m3u8
Other link like this works in both:
https://d2ufudlfb4rsg4.cloudfront.net/bloomberg/IIrcyflxg/IIrcyflxg_medium.m3u8
Then, my question is, why Safari can play a video with CORS issue but Chrome not?. Or how Safari avoid the CORS issue? to try to reproduce it in Chrome.
CORS is enforced by the browser, not the server. So it’s up to the browser whether the resource is blocked or accessed. In the case is chrome, the video segments are downloaded via XHR, and therefore are handled by the browser HTTP stack. In the case of safari, which natively supports HLS, the segments are downloaded by the media player directly, bypassing the browser, and thus CORS.
This behavior can not be reproduced in chrome.
I've been using jplayer jukebox for some time with no problems but it has suddenly stopped working in Chrome. Still works fine in IE and Firefox but the playlist no longer shows in Chrome. It was definitely working at the end of June 2014 when I last added a track. webpage is http://www.jonphilibert.com/gallery.htm
Any suggestions gratefully received
Hilary
Try changing the "mp3" to "M4A".
https://groups.google.com/forum/#!topic/jplayer/Lyk7Znv1pWE
What has happened is that this Chromium issue means that Chrome uses Flash for playback since Chrome 36, rather than HTML5.
Your problem is that the path to the SWF path is set up incorrectly - Chrome Console tells me "GET http://www.jonphilibert.com/Jplayer.swf 404 (Not Found)"
So once you configure the player to have the correct SWF file path, playback should start working again in Chrome.
Note this means that playback also won't be working in other browsers that don't support HTML5 audio.
I've seen this post on Google's product forums, but who knows when that will be answered, so hopefully someone here may know.
On my site, the video will not display in Chrome (latest). It works fine in IE[x], FF, and Safari. In Chrome, the console shows this "warning":
[blocked] The page at https://www.mightyspring.com/ ran insecure
content from
http://www.youtube.com/v/cFxF3lWsdPE?enablejsapi=1&playerapiid=homepageVideo&version=3.
Anyone have any idea what's wrong and/or how to fix it? Or is this just a bug that will fix itself in the next release?
Just in case anyone comes across this issue, the answer is because Chrome is properly blocking the site from loading a video not behind SSL. My live site is actually https:// (see the "s"?) and I had the protocol as http://