Comments on: WordPress (nginx-varnish) Jetpack xml_rpc 32700 glitch fix

By: John

John — Thu, 22 Feb 2018 10:15:18 +0000

I was facing this glitch for quite some time. This workaround works. Thanks.

By: Brandon Kraft

Brandon Kraft — Wed, 05 Oct 2016 21:36:56 +0000

Howdy! I’m from Jetpack support. There are a couple of ways around this issue.

If your server uses the `HTTP_X_FORWARDED_PORT` value on the $_SERVER variable, we will use that port number.

Alternatively, you can set define( ‘JETPACK_SIGNATURE__HTTP_PORT’ , 8080 ); in your wp-config.php (where 8080 is whatever port PHP has as $_SERVER[‘SERVER_PORT’];

By: dp

dp — Wed, 04 May 2016 08:04:44 +0000

The $_SERVER['SERVER_PORT'] = 80; did it for me. Thank you for sharing.

By: Chris R

Chris R — Fri, 04 Mar 2016 02:24:30 +0000

Not sure if an update changed things, but this doesn’t work for me. I’m running this exact setup (I am running php 7, but don’t think that’s an issue).

However, I do not have the “nano /etc/nginx/conf.d/yousite.conf” file.

Also, tried adding the “if (req.url ~ “wp-(login|admin)|preview=true|xmlrpc.php|minify.php”) { return (pass); }”, but couldn’t get it to work. I’m still learning, so maybe I didn’t put it in the right spot? I get an error when starting the service.

By: Pedro Nariyoshi

Pedro Nariyoshi — Sat, 10 Oct 2015 02:12:53 +0000

Sure, go ahead. (;

By: hasnain

hasnain — Mon, 08 Jun 2015 12:15:52 +0000

this thing is not working for my site as i m unable to find nginx in etc folder

By: The Pirate Web

The Pirate Web — Sat, 07 Feb 2015 12:55:24 +0000

Thanks,
It worked for me
<3

By: Nelson/Roberto

Nelson/Roberto — Thu, 11 Dec 2014 14:24:10 +0000

I think I’ve found a more permanent solution. If the fix works for other people I’m hoping this post will can get updated since a lot of sites link to it.

First you must disable caching as Pedro suggested. My configuration looks like this:
if (req.url ~ "wp-(login|admin)|preview=true|xmlrpc.php|minify.php") { return (pass); }
Then you have to tell jetpack to use port 80 in your wp-config file.
$_SERVER['SERVER_PORT'] = 80;
Once you update your wp-config you might get a 404 error, but that went away for me and now jetpack works perfectly.

Hat Tip to Justin Soo for the solution. http://juzhax.com/2014/08/connect-to-jetpack-using-behind-varnish/

By: Enlightenment Documentation: Setting up and managing the Jetpack Portfolio - Reader

Tue, 02 Dec 2014 19:45:40 +0000

[…] error, it usually means you are using a proxy or caching server like Varnish that needs to be temporarily disabled until the connection is […]

By: eswaribai

eswaribai — Wed, 23 Jul 2014 07:34:08 +0000

This worked for me. Thanks for the code snippet {Pedro Nariyoshi}