Error 400

Thank you. I was able to reproduce this issue on your installation.

Mark, please submit your details again.
We’ll need FTP access so we can run diagnostics on your installation.
s2Member® » Private Contact Form

Hi Jason,

Great (at least from a troubleshooting standpoint). I’ll set up the FTP account and submit now.

Bendix – we’re in the States, so I’m not sure what is going on. Perhaps when we get to the bottom of it we can help you as well.

@Mark R.
Investigation completed. Thanks for your patience.

I found that your installation of PHP was running in SAFE MODE, which has some side effects in WordPress, and triggers an invalid internal redirection due to a bug that exists in the WordPress WP_Http class. I’ll save you the rest of the boring details related to this minor WordPress bug.

Long story short, we’ve found a way to work around this issue in the release of s2Member v120309, by forcing a WP_Http redirection value of 0 during Amazon S3/CloudFront configuration. This allows s2Member’s auto configuration routines to also succeed in PHP installations running in SAFE MODE.

Your test WordPress installation has now been fully configured with Amazon S3/CloudFront. If you have other installations that you’d like to integrate, please make sure that you upgrade to s2Member v120309 first, or disable SAFE MODE in your /php.ini file. See Also: http://php.net/manual/en/features.safe-mode.php

See Also: s2Member® Unified Changelog » v120309

Thanks Jason –
That does make sense. I did both – changed to non-safe mode, as well as upgrade.

Of course, the site you tweaked and got working was the temp site – without any content. I copied back the basic code (not much really – plain install with s2Member plugin and some content and theme), and I got this error when updating to CloudFront:

Unable to auto-configure Amazon® CloudFront Distributions.
Error code: 409. Error Message: Unable to create Amazon® CloudFront Downloads Distro. Unable to create Amazon® CloudFront Downloads Distro. Conflict

At least it’s a DIFFERENT error – perhaps this one is easier to troubleshoot.

** UDPATE **
Well that was easy – it was obviously a conflict since those CF settings we already manually set up. Once I deleted those, it created them again perfectly with the correct settings. WONDERFUL.

THANKS JASON!

• This reply was modified 4 years, 10 months ago by  Mark R..

Jason!!!!!
thank you very much!!!!

Amazon® CloudFront Distributions auto-configured successfully. Please allow 30 minutes for propagation.

:)

Two with one stone – nice job.

Thanks very much for the confirmation guys! We’re glad you got that working finally. :)