I have an issue that is occurring if you try and seek a few times to different points in the video. Eventually you end up getting an error saying it's a network issue. If I download the file from the server it's fine and if I don't seek to much it's fine as well.
Wondering if anyone knows what the issue might be.
Here is an example: https://www.la1tv.co.uk/player/107/195
Just jump around a bit (in chrome) and you should get the error. I have attached a screenshot.
Thanks!
error screenshot
The issue was that I was not sending a header with an etag in the response containing the video. Adding the etag header (which in my case is the file id) solved the problem.
Here is some information about etags: http://en.wikipedia.org/wiki/HTTP_ETag
Related
Earlier this week the video content we use in our Test and Production environments, which is using https://player.vimeo.com/external/... links, has been throwing a bunch CORS errors in the console after loading the very first part of the video.
Sample error:
The 'Access-Control-Allow-Origin' header has a value 'null' that is not equal to the supplied origin.
The initial request we make out to player-vimeo.com does have Access-Control-Allow-Origin:*, as expected from the configuration of our application. However, that player-vimeo returns a 302 which redirects to the CDN https://vod-progressive.akamaized.net and the response we get from there has Access-Control-Allow-Origin: null.
We have not changed any of the code around this video content in months and we've been using Vimeo this way for a long time. It seems to happen in Chrome, but doesn't happen, or happens very rarely, in FireFox or on Mac. The only solution we have found so far is to remove the attribute crossorigin="anonymous" from the video tag, but that is not ideal as it breaks the getting of the caption files associated with the videos.
Weirdly, if you let the video throw the CORS error many times in a row, it actually starts working after it has thrown the error enough times.
As far as we can tell nothing we've done would have led to this breaking, it seems as if Vimeo isn't passing on the Access-Control-Allow-Origin param anymore, or somehow akamaized.net is losing it.
UPDATE
We heard back from Vimeo support 6/10/2021:
“This is an issue that our developers are aware of and are working to fix. We apologize for any inconvenience caused and appreciate your patience.
We’ll reach back out once this issue is resolved.”
One day youtube stopped working on all browsers. It loads preview of the video and then loading infinite circle appears. Sometimes it shows the message: if playback doesn't begin shortly, try restarting your device. I cleared coockies, history etc. two times. I found something about the hosts file, but the original file contains the same exact thing the guide was recommending to replace. There similar problems with youtube, but i didn't find anything that could possibly solve the issue except the host file.
Whether the problem only occurs on the YouTube site? Try to play some online video from another site, such as Bing and Google.
If this issue only occurs on the YouTube site, perhaps the issue is related the YouTube site, you could check the YouTube help forum and contact with them.
If another site also has the same problem, perhaps the issue is related to your network or computer. Please check the network connection and check which version of OS and Browser version are you using? Then, try to Restart your browser, Restart your router, Restart your computer or Update your browser to the latest version.
Make sure you use propper audio device.
I have a couple of video-requests to an s3-bucket. the last two are cached.
Every not cached request had the expected cors-headers:
Once the video is cached, the cors-headers are missing and it comes to the well known cors-policy error:
It's only reproduceable in windows-chrome, everything works fine on my mac.
Does anyone have the same problem? Is it a browser-bug or am I able to set anything in the bucket to prevent this problem?
So after making a website using VScode (Probably not important) and uploading it to GitHub Pages, the website looked great! It was doing fine on windows and on my phone, everything was looking good.
Then, after checking it on my Mac with Safari (Not sure which would be the issue but I presume Safari) the css seemed to be a little weird and the page layout was all over the place.
After checking the console I am getting the following error
Failed to load resource: the server responded with a status of 404 ()
This is my styles.min.css file so I presume this is the issue.
Checking the console on windows doesn't bring around any errors which leads me to believe that this is the error...
Does anyone have any idea what could be causing this?
I'll post some pictures of what is happening to the items within my website.
Since people want the code, hopefully posting the website so you can inspect it will be fine? There's a lot of code and I'm not sure where to upload it.
https://manakura.github.io
EDIT 1: After checking out the code in the console, it seems like it has something to do with the width of the text? Because if I change the class from >col-md-4 to >col-md-3 which has less width the page is fixed.
Though I'm not sure how to fix this with col-md-4 or if I will have to enter some kind of media query?
Website working in Chrome on MacOS
Your problem is that there is no file actually named styles.min.css in the Github repo. You need to create a file first.
I am a google chrome user, almost 90% of the time this browser works best for me, but most oftenly i face an issue and that is while downloading the videos, which are big in size like 400 mb or above, what happens is download proceeds till 80-90% then some error message appears and everything downloaded just gets vanished, this is while downloading videos from MVA, so i wanted to know if it is an issue with the browser or with the server, but i face it almost everytime, according to me its not the server issue.
If anyone can explain.
Yeah and I forgot to specify the error, actually the error is unknown.
The Image of the error is shown here:
And this happens very time i try to download any big video, and i have even encountered this error while downloading big application, well anything big in size lands to this problem.