Request headers for a couple of videos I use in production that have problems off and on (grouped by site):
01FXMFJNS18XE03V3JAA0YYCXG
01FXMFMSCT29D6M06M3TQZF5QG
01FXMFNQY7HVCDP1P5N7XKPQJG
01FXMFPY78YPS72CC93N7RDFZ1
01FXMFQPDYFNQ71DX4VFTMNM0P
Some of these videos show up as canceled in my network inspector. None of them have audio. Some 3MB background loops are playing, and other 1.5MB videos are not. They all have exactly the same codec, compression etc etc, if that’s of any use.
non of them have audio
band-horses-video.mp4 has audio
<video class="embed-responsive-item" autoplay="" muted="" loop="" controls="">
<source src="/videos/band-horses-video.mp4" type="video/mp4"></video>
I was talking about my own videos of which I just shared the id’s
same problem here with my websites, some of the videos stopped working in the main page 24hours ago without any reason
I also have similar problems, I changed nothing to my code but this weekend I noticed that my videos weren’t showing anymore. You can see it at website with broken videos; there should be videos playing in the “examples” section and in “how it works” section. I tried to deploy it again, but the problem remains. Does it help if I also share my x-nf-request-id headers?
For readers facing the same errors. I solved this issue temporarily by renaming the video and running the command git lfs push --all origin. I’m not sure why this work but this workaround made the video appear again. Still, I am waiting for a permanent solution from Netlify.
We have rolled out a fix for this issue and all videos should be correctly returning the range of bytes requested now.
I’ve tested several of the reported URLS and sites above. All the ones that were reported as not playing are all working correctly now when I test (even older deploys that did not work before do work now). For example, @SuzannaWentzel, I checked the site you posted and the videos are working for me now.
@jprivillaso, I think your git lfs push just happened to occur around the same time this fix was rolled out. That command would not have caused any change to the CDN behavior. I do think this was just a coincidence that this command was run at the same time the fix was rolled out.
Please do let us know if you see any videos not playing now or any incorrect data sent by the range header now. This should be fixed for everyone now and if not we really do want to know about it.
hi @luke
all videos are approved 
Thanks
Wow. This would be such a coincidence. In any case, I can confirm that the videos are working.
All videos are working fine again, thanks @luke!
Everything’s working for me now. Thanks!
Awesome, thanks @luke!