Issues with Amazon S3 / Digitally signed URLs

And! Sorry…

I re-downloaded the latest s2M plugin and replaced what was on the server. Just for good measure.

Thanks for the feedback. I’m adding a note here about IAM so this can be retested shortly. See: https://github.com/WebSharks/s2member/issues/173#issuecomment-44387014

This issue at GitHub has been updated. Please take a look when you get a moment. Thanks! See: https://github.com/WebSharks/s2member/issues/173#issuecomment-44518844

any updates on this — seeing similar issue.

@jhall_3rd The investigation here turned up nothing useful I’m afraid. https://github.com/WebSharks/s2member/issues/173#issuecomment-44518844

What is the issue that you are having exactly? If you can add steps to reproduce here, that’d be great! ?? https://github.com/WebSharks/s2member/issues/173#issuecomment-44518844

have been online with amazon support for 2 days trying to find out why s2m is restricting ip that is requesting a s3/cf file.

We decoded the Policy s2m used to sign the URL and found that it is using the server’s IP in the AWS:SourceIP

This is causing an access denied when accessing the signed URL since the IP won’t match.

For ex upon decoding the signature associated with a file download we get this:
{“Statement”:[{“Resource”:”https://d3od88nicba67t.cloudfront.net/SD-os-gringos-parte-1-DOWN-SD.mp4″,”Condition”:{“IpAddress”:{“AWS:SourceIp”:”207.210.203.168/32″},”DateLessThan”:{“AWS:EpochTime”:1424884195}}}]}

207.210.203.168 is the IP of the server and not the client

Filed a trouble ticket in s2m just now.

207.210.203.168 is the IP of the server and not the client

If you run the following test, what does it produce?

<?php echo $_SERVER['REMOTE_ADDR']; ?>

207.210.203.168

I see, thank you. So the issue is that your server environment is reporting an incorrect value in this variable. <?php echo $_SERVER['REMOTE_ADDR']; ?> should report the client’s IP address, and <?php echo $_SERVER['SERVER_ADDR']; ?> should report the server’s IP address. It appears that this might be reversed on your hosting platform.

You might want to run the s2Member Server Scan tool. It can help you diagnose things like this. See: https://www.s2member.com/kb/server-scanner/

but this gave me MY IP:

<?php echo $_SERVER[‘HTTP_X_FORWARDED_FOR’]; ?>

So you are behind a proxy or load balancer. I suggest adding the following line to the top of your /wp-config.php file.

$_SERVER['REMOTE_ADDR'] = $_SERVER['HTTP_X_FORWARDED_FOR'];