- This topic has 6 replies, 2 voices, and was last updated 12 years, 2 months ago by .
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › eStore product download – Amazon S3 downloads using hosting bandwidth
Tagged: amazon s3, bandwidth, Download, estore, image downloads
We’ve got an Amazon S3 download set up on our eStore for a couple of products. The download is a 2 GB video file. It seems that, despite the fact that we’ve got all of our S3 credentials in line, we’re still seeing the bandwidth going through our website hosting supplier (GoDaddy), to the tune of 240 GB yesterday alone. My impression is that these data transfers should be registering with Amazon’s servers only, right?
Also, we’ve run into some big-time site slowdowns in the last few hours. A call to GoDaddy told me that what they were seeing as a “Digital Downloader” plugin was at the root of the slowdown, which should not be in play because of the Amazon S3 activation. Any help getting this straightened out would be great.
Website is here: http://buy.jeremypowerscrosscamp.com
More info: We’re on WordPress 3.4.1, eStore 6.8.5, and the slowdown is happening everywhere, frontend and backend.
You need to follow the S3 integration instructions here.
When properly configured, S3 downloads should be consuming ZERO bandwidth from your host.
I’m fairly sure I followed those instructions to the letter but am still seeing host bandwidth. Not sure what the issue is but I’ll keep trying. Any ideas on the site slowdown?
Check the product URL fields. You MUST use AS3TP and ***NOT*** HTTP for the URI scheme, as described in the integration instructions.
It will be clear to you if you watch the video tutorial.
It’s definitely set up as AS3TP. I ran into that issue before, where it spits out raw XML, but before anything went live so that’s not the problem.
Please enable the debugging and try a test. Then look in the download_manager_debug.log file. What does it say?