Jetpack for WordPress – xml_rpc-32700 doesn’t connect to WordPress

I recently started up this blog on an EC2 instance. It uses nginx, php, varnish, mysql and Wordpress. It worked a charm, until I wanted to configure Jetpack for WordPress. The problem I was having was that xml_rpc-32700 wouldn’t connect to WordPress.com.

I did a little research and with the help of Mokah, we fixed the issue.

These are the step we took to have the system correct the problem for us:

First Step

SSH into the instance

Second Step

Access the nginx configuration file to change listening ports using this command:

nano /etc/nginx/conf.d/yoursite.conf

 Third Step

Once you are in your configuration file, change ‘listen 8080;’ to ‘listen 80;’.

Fourth Step

Save the file and stop varnish using the following command:

service varnish stop

Fifth Step

Reload nginx using the following command:

service nginx reload

Sixth Step

Now you can connect your Jetpack to WordPress and authorise the connection with your WordPress user details.

Seventh Step

Now that you have connected to Jetpack, you need to change back the port form 80 to 8080 for nginx to function correctly. Use this command  to access the configuration file again:

nano /etc/nginx/conf.d/yousite.conf

Eighth Step

Change ‘listen 80;’ back to ‘listen 8080;’, save the file and then close it.

Ninth Step

Now reload nginx using the following command:

service nginx reload

Tenth Step

Finally start varnish back up using the following command:

service varnish start

This should fix the Jetpack problem and will let you connect to WordPress.

Thanks for reading!

Facebook’s acquisition of Instagram looks like a waste of a billion dollars

Facebook acquired Instagram in April for a billion bucks. People had a lot to say and had already knew that Instagram had fallen into the wrong hands, especially when it comes to privacy concerns.

Well, Instagram and it’s parent company Facebook, have just destroyed the last bit of privacy Instagram had. They’ve changed their privacy policy to give them the rights to sell user’s pictures along with the right to share user information with Facebook and other affiliates.

WHAT A DOUCHE BAG OF A MOVE!

Instagram have given us a deadline in which we could delete our accounts. January 16th is the final date to opt out otherwise you’d be tied in.

What a few people had to say about Instagram’s little f*** up :

The common moves I am seeing now is over to Flickr. Personally, it’s not as easy as it was using Instagram, but at least your shit ain’t gonna be sold on.

All we can say to Instagram is, good luck with the suicidal move…well America is the land of the free and home of the brave. (I’d advise Instagram not to hold their breathe.)

Hello World.

Hello people.

I had this random little domain sitting in the domain bank and thought I should make some use of it.

First of all I want to say that this bad boy is running on an EC2 T1 micro instance with the simple, but clever use of nginx, Ubuntu and Varnish. (By the way if you want to learn how to run a WordPress blog at lightning speeds, you got to check this blog out!)

Back to the domain business. I guess you’re thinking what the f*** does ‘vqev’ stand for? Well, you can call it what you like. I call it a 4 letter .com domain name that you don’t have. ;-)

Anyways, I’ll keep this first update short and I’ll be back soon with some more random nonsense to talk about.

Peace!

oh yeah! If you have Twitter follow me!