Tips and Tricks HQ Support Portal › Forums › WP Lightbox Ultimate › Lightbox ultimate – Error message "flash: Video file not found"
- This topic has 9 replies, 5 voices, and was last updated 10 years, 2 months ago by
wpCommerce.
-
AuthorPosts
-
February 11, 2014 at 5:45 pm #10520
guyassaf
MemberHello,
I’m using Amazon/s3 and trying to stream a protected video to my site.
The message I get when playing the video is ” flash: Video file not found”
As seen in this page [http://www.biores.co.il/video2/]
I’m using this shortcode
[wp_lightbox_embed_protected_s3_video name=”allergy.mp4″ bucket=”biores” width=”” height=””]
I’m sure the name and bucket are correct as much as I can.
Trying to find the problem, I add permissions to everyone and still the same problem.
Thanks.
February 11, 2014 at 11:03 pm #60817wpCommerce
ModeratorHi, when I access your video I get an error response from Amazon S3:
<Error>
<Code>InvalidAccessKeyId</Code>
<Message>
The AWS Access Key Id you provided does not exist in our records.
</Message>
</Error>Please make sure that you entered the following information correctly in the Lightbox Ultimate Settings:
1. AWS Access Key ID
2. AWS Secret Access Key
February 12, 2014 at 8:56 am #60818guyassaf
MemberThank you, this was the problem.
For some reason the keys removed.
March 17, 2014 at 4:51 am #60819NikkiBrown
MemberHello,
I am having the same problem with getting this error (“flash: video not found”). I have re-entered the access key and secret key, but no luck. Could you possibly take a look?
[http://www.easttxcomputerhelp.com/join-us/website-123-basics/website-123-basics-lesson-1/]
The short code I am using is [wp_lightbox_protected_s3_video name=”How-to-Buy-a-Domain-Name.mp4″ bucket=”ETCH-Website-123-Basics” width=”640″ height=”480″ source=”http://www.easttxcomputerhelp.com/wp-content/uploads/2014/03/M1-V1-How-to-Buy-a-Domain-Name.jpg”%5D
I am pretty new to using Amazon s3, so maybe I am doing something wrong. If I make the video file “public” and click on it in S3, it downloads instead of opening up in a player in my browser. Is that normal or do I have the file stored incorrectly somehow? I am using a Mac and the Safari browser.Whether I have the file set to “public” or “private” in S3, it still gives me the same error when I try to play it on my site.
Any advice would be appreciated.
Thanks!
March 17, 2014 at 1:37 pm #60820wzp
ModeratorYour bucket name does not conform to Amazon’s bucket naming rules; specifically, bucket names must contain lower case letters only:
[http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html]
March 18, 2014 at 3:47 am #60821wpCommerce
Moderator@NikkiBrown, please take a look at the following post which will help you troubleshoot this issue:
June 25, 2014 at 5:41 pm #60822sophie1
MemberHello,
I have been using the lightbox plug for a long time, with Amazon S3. Recently, I have started getting the “flash: video not found” message. But if I reload the page, the video usually plays, so I’m assuming my S3 access codes are not the problem. Site is barnyardbirthday.co. I did recently purchase the flowplayer commercial version, and you folks were kind enough to tweak it for me because the logo was not displaying. Appreciate all your help.
thanks!
June 25, 2014 at 11:29 pm #60823wpCommerce
Moderator@sophie1, what value have you specified in the “AWS S3 Video URL Expiry Time After Page Load” field? It’s under
Settings->WP Lightbox
.June 26, 2014 at 12:18 am #60824sophie1
MemberNone. Do I need a value there? All my videos are 2 minutes long. Does that mean that I just need a value longer than 2 minutes? Thanks.
June 26, 2014 at 1:13 am #60825wpCommerce
ModeratorIf you do not specify any value it will set the option to
300
(5 minutes). That means once the page loads all the video links will be valid for 5 minutes. You can specify a higher value if you want the links to be valid for longer. For example:900
( 15 minutes),1200
(20 minutes). This prevents any user from hotlinking your videos (because the links will expire after a certain time). -
AuthorPosts
- You must be logged in to reply to this topic.