Wowza Community

Mediacache S3 301, 302, and 307 redirects

Hello, I’ve spent many hours in vain trying to get wowza mediacache to work with S3 MP4s. I’ve tried it on Amazon S3, Vultr S3, and DigitalOcean S3, and none of them work.

I’ve enabled the debugHTTPRequests on all three, and the net result is the same: the log either shows 301 (vultr), 302 (DigitalOcean) or 307 (Amazon) redirects. It seems wowza doesn’t follow the redirects? Unfortunately the wowza logs don’t show what the redirect is TO, just that I’m getting a redirect.

After the redirect I get a “MediaCacheItemBase.init: Item does not exist” in the log.

I know the API keys are fine because I can mount drives to them and access the files okay. The problem appears to be in Wowza.

I’m using the current release 4.7.8 build 20191105123929.

Any suggestions on how to get this working?

Thanks.

Hi @Charles Gaefke, you have this set up as a VOD edge application correct?

Also, many times this is a case of a simple spelling mistake:

amazon3/ vs amazons3/ in the url

http://[wowza-ipaddress]:1935/mediacache/_definst_/mp4:amazons3/sample.mp4/playlist.m3u8

If you are still having issues after referencing the examples in this MediaCache complete guide, please do submit a support ticket and we will take a look a the config and get it working for you.

Hi @Charles Gaefke, you have this set up as a VOD edge application correct?

Also, many times this is a case of a simple spelling mistake:

amazon3/ vs amazons3/ in the url

http://[wowza-ipaddress]:1935/mediacache/_definst_/mp4:amazons3/sample.mp4/playlist.m3u8

If you are still having issues after referencing the examples in this MediaCache complete guide, please do submit a support ticket and we will take a look a the config and get it working for you.

Thanks.

I managed to get the Amazon one working by manually setting the region and setting the awsSigningVersion to 4, as listed here:

https://www.wowza.com/community/questions/44299/mediacache-aws-s3-not-working.html

It would be nice if Wowza defaulted to this and the documentation was updated accordingly!

Excellent information and thank you so much for sharing that. I will request this change in documentation today. Thanks again @Charles Gaefke for the feedback and glad you got it working.