-
Hi Helpdesk,
Please note that when the URL is formed using cloud front domain name , getting the following error. If the normal URL is there then the problem goes away.
Please have this fixed and update the wordpress site as I have a lot of videos uploaded already on S3 and now having to do the MP4 Fast Start is not a viable option. It is working fine without the cloud front URL attached as prefix to URL. You had provided a similar fix earlier request you to do the needful for this issue as well.
which are working with the normal URL but not when cloudfront domain is attached in front of it.
1. URL Has issued due to cloud front [fvplayer src="https://video-cdn.eturnti.com/TABDC/TFinal.mp4"]
2. URL that is working fine when there is no cloud front domain attached infront of the URL.
[fvplayer src="https://s3.ap-south-1.amazonaws.com/S3-videos/TABDC/TFinal.mp4"]Thanks,
Kiran
-
-
Hello Kiran,
are you checking the HTTP referrer on your CloudFront distribution? That could be causing the issue.
Also, the SSL on video-cdn.eturnti.com appears to be wrong. That could be causing the issue as well. I set our Video Checker to ignore SSL errors now, it might be helpful on staging websites which might have a self-signed certificate.
Thanks,
Martin
Hi Martin,
I am not checking any HTTP referrer headers just followed only the fvplayer documentation as of now.
No SSL related changes. Please let me know where your code changes are kept for me to use for the wordpress website where you are ignoring those errors. Want to use it in my site as a fix.
Please find attached my settings for cloudfront and let me know if anything is amiss.
https://www.screencast.com/t/6nfm5efjb3f
Thanks,
Kiran
Hello Kiran,
so it must be the wrong SSL. I can see on your screenshot that you are using the default SSL certificate with a custom domain, which just can’t work.
Instructions for setting up a proper SSL for CloudFront can be found here: https://foliovision.com/player/video-hosting/serving-private-cloudfront -> “Now you can enter your domain which you will point to your CloudFront domain (use C Name record in your DNS Zone).”
The fix which I did has been done to Video Checker which is a service we provide for FV Player users.
Thanks,
Martin
Hi Martin,
Thanks for the reply. I have done the SSL configuration and the certificate is using the CNAME details . The certification manager screenshot clarifies this .
https://www.screencast.com/t/82p5aBGy8Fxf
The actual issue is that without the Cloud front URL prefix the video is working with just the S3 bucket details but not working with a simple S3 URL as pointed out in the original issue thread.
The cloud front url is working for a lot of videos. The videos which work with given the full S3 bucket path when prefixed with the cloudfront URL is giving these issues the start of the video error.
Please help me resolve this. There are around 10 videos very long ones uploaded to S3 bucket cannot repeat the painful exercise of MP4 Fast Start , as these videos are perfectly working fine from the S3 direct path. They have issues only when the cloud front domain alais is provided.
Also the cloud front URL is working fine with certain videos from S3. Only some are showing this issue.
Where is the fix for the fvplayer pro plugin fix shall pick it from the location as you said you are now ignoring SSL errors. This may not be the case as the certification manager is showing.
Thanks,
Kiran
Hello Kiran,
if you fixed your files on S3 after finding out about these issue with our video checker while using the CloudFront URL, then perhaps CloudFront is still holding the old files in its cache. Here’s how you can clear it: https://foliovision.com/player/video-hosting/hls#clearing-cloudfront-cache
The fix which I was mentioning has been done to the Video Checker which is a service we provide for FV Player users – it’s the “Admin: Video OK” message which you see in top left corner of your videos. And we fixed it to accept bad SSL certificates to help you sort out your videos issues in development environments before getting real SSL.
Thanks,
Martin
