houldsworth1

I retract my previous statement. After some additional checking I discovered that WP Super Cache, which I had previously installed and then disabled, was still causing the old pages to be displayed.

As soon as I

uninstalled

WP Super Cache instead of just disabling it everything worked as expected.

Apologies for the confusion

Do you havea firewall enabled? Perhaps you could disable it temporarily to see if that is the issue and try again?

There is another post on here with options. One of the replies was as follows:

It looks like your web server is incapable of sending outgoing requests over HTTPS (as opposed to HTTP). Jetpack should be able to detect this inability and work around it. We’ll work on making that check better in the next version of the Jetpack plugin.

In the meantime, if you are comfortable editing PHP files, you can modify wp-content/plugins/jetpack/jetpack.php.

On line 1290, change the current:

if ( $jetpack->use_ssl[$method] ) {

to the new:

if ( false && $jetpack->use_ssl[$method] ) {

I tried that on my Amazon EC2 instance and it worked!

I had this running a Bitnami instance in Amazon EC2. I tried the suggestion listed above by atobias (change line 1290 of the PHP file) and that worked.

Thanks!

I get the same error. I fired up a Bitnami WordPress instance in Amazon’s EC2. Installed the plugin without problem, but now I get this error.

The site is definitely visible as I can access it. Does anyone know if specific ports need to be opened for this to work (I know that Amazon locks everything down unless you specifically open it up).

Thanks!