-
Hello. Foliovision team.
I heard the “Video file not found” error from the customer today and checked the problem.
Almost all of the videos are played for 15 to 20 minutes and then show the above error.
In some cases, an error message may appear as soon as you start playing the video.
I am using a Vimeo Dash. So far I have not had this problem.
I have the same problem when I tested it on another site because of this problem.
I have tested Chrome, Firefox, and Edge and they all play the same for 15-20 minutes and then I got an error message.
When an error message is displayed, reload the page and repress the play button, the error message come again.
After about 10 minutes or more, the page must be reloaded for playback.
Testable addresses are attached below.
http://linedraw.co.kr/test-video/
http://linedraw.co.kr/freelesson/The link below uses a different version of the plugin, but the same error occurs.
http://3d.linedraw.co.kr/test-video/
-
-
I have the same problem when I tested it on iOS10.
After playback for about 15 ~ 20 minutes, the video stops.
And “Please reload the page and try again” message appears.
I tested the link below.
Hi Gbrother,
Vimeo is having some kind of issues with the MPEG-Dash streaming. Could you please temporarily turn it off and see if the videos work on your devices without it?
Thanks,
Eduard
Hello Gbrother,
We have just released the fix for the Vimeo CDN switching in the latest update. All you need to do is to upgrade the Pro plugin to version 0.8.27 and the MPEG-Dash streaming should work properly.
Just follow this process to check if it works correctly:
- Play the video
- You should be able to see “FV Player Pro: Preloading {video id} of video/fv-mp4 type” and “FV Player Pro: MPEG-DASH found!” in browser console
- Now you can check m4s files in browser developer tool’s network tab. You will probably get these from skyfire.vimeocdn.com
- If some segment fails to load 4 times you will see that in the nework tab and you will also see “FV Player Pro: MPEG-DASH error, retry 1!” on console
- That means the fallback is activated and you should see “FV Player Pro: Preloading {video id} of video/fv-mp4 type” on console again
- This time it will play the second MPEG-DASH stream – on the network tab you should see m4s files coming in from 45skyfiregce-vimeo.akamaized.net or something similar, but not skyfire.vimeo.cdn
- If that also fails, you will see “FV Player Pro: MPEG-DASH error, retry 2!” and it will fallback to MP4 file as last resort
Please let us know if the fix worked.
Thanks,
EduardI have another problem after update.
There is error when I click play button in video “Please reload the page and try again in a couple of minutes. null”.
It cant be played even I reopen the video page. Almost 1 in 10 videos cant be played.
I put example link below.http://linedraw.co.kr/test-video/
And randomly error occurs with “Please reload the page and try again in a couple of minutes.” and video can be played after few minutes when I reopen the page.
Hello Gbrother,
I apologize, I forgot to add that you have to be in the Beta mode to make the fix work.
Thanks,
EduardHello Eduard.
I’ve set beta mode.
The “Video file not found” error seems to disappeared.
But the above-mentioned “Please reload the page and try again in a couple of minutes. Null ” error occurs in some videos and is not playing at all.
And this problem “Please reload the page and try again in a couple of minutes.” is also happening randomly.
Hello Gbrother,
I checked your video and got the same error you have described. Could you please turn off the Turbocharge Ajax Vimeo loading option in Vimeo settings and test it without it?
Thanks,
EduardHello Eduard.
I turned off the Turbocharge ajax option and tested. The same error occurs.
Hello Gbrother,
Thanks for the testing. We’ll keep looking into this issue and let you know when we have a solution.
Thanks,
EduardHello Gborther,
I had a look and I can’t get your video to play. Are you sure it still exists? Seems to me it was removed or its privacy settings were changed (see our guide https://foliovision.com/player/video-hosting/how-to-use-vimeo#privacy ), so we need to fix our detection for that.
Please try to open thatt when you log in to Vimeo and see if it plays.
Please try to embed any other video you can find on Vimeo.
Thanks,
MartinHello Martin.
The vimeo setting is fine.
The vimeo embed code works as expected. An error occurs only when I insert the fvplayer code.
I put the vimeo code and the fvplayer code of the same video on the test page.
Only vimeo is played. This problem occurs in some videos.
The customer says that he has not played for several days.
Hello Martin.
After a few tests, I noticed what video was causing the problem.
Short time videos do not cause problems. Video is about 10 to 80 minutes long. If the video is over 90 minutes in length, all of the videos have errors of “Please reload the page and try again in a couple of minutes. Null “.
I uploaded a short video and over 90 minutes of video to Vimeo and embedded them on the site. All videos over 90 minutes occur error “Please reload the page and try again in a couple of minutes. Null ”
The video on the test page that I showed is over 90 minutes.
It seems that there is something different in the way of playing videos over 90 minutes.
Please confirm. Thanks.
Hello Gbrother,
I have no issues with playing log vidoes, such as https://vimeo.com/8458060 (55 minutes) or https://vimeo.com/23849197 (1 hour and 43 minutes).
But I see it plays using Vimeo iframe. I found the issue is related to the video privacy settings. I’m working on a fix now.
Thanks,
MartinHello Martin.
The error I mentioned above is from 2016 onwards, and the new uploads now have problems. In the videos uploaded before the beginning of 2015, there is no problem as you said.
The two videos you said were uploaded six or seven years ago, so there is no problem.
Please upload a new video to Vimeo and then test it. It would be helpful to refer to the above problem.
Hello Gbrother,
I put in a fix on the API server and now it works. The issue was that there was too much data in the API response and our plugin uses regex to do some basic parsing on it – and that was just failing because of the size of the string.
So the quick fix is in, but we will have to redo the way we handle the secondary CDN for MPEG-DASH. Currently the fallback if the DASH stream fails is that goes to MP4 video at least.
Thanks,
MartinIt works very well.
Thank you for your quick support.
