Unkonwn Error from Jetpack Debug

Hi @foxfireforge

On both https://fenric.com and https://sawasta.com when I make a cURL request I receive the same error on both:

HTTP/1.1 409 Conflict
Date: Mon, 25 Oct 2021 15:22:32 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 83
Connection: keep-alive
Server: Apache/2
Age: 1

This seems to be an issue with your hosting. Can you check with your host about any reason why would be seeing that response on the `xmlrpc.php. file?

I really don’t understand how it could be the anything from Verio… all three sites are side-by-side on the same server.

/home/apo/blah/blah/verio/huge/long/path/users/me/ffforge
/home/apo/blah/blah/verio/huge/long/path/users/me/sawasta
/home/apo/blah/blah/verio/huge/long/path/users/me/fenric

One works, two don’t: it pretty much has to be something in the WP setup, but I don’t understand what to even look for. This is the first time in my life I’ve even seen HTTP 409… Is there any tip on what to look for that might be different in the sites that don’t work?

Hi there, @foxfireforge,

Unfortunately, we can’t tell you much about that as we don’t have direct access to the servers to see what’s going on.

Have you reported this to the host? Sometimes it’s a matter of a block to be taken off, something similar to a mod_security type of block. But again, we can’t really say from our place.

Hope that answers your question!
Let us know how it goes with your host, and we’ll be happy to run more tests on your Jetpack connections.

Update:

Sometimes it’s easier to try to break the one that works as an experiment. Except… I haven’t been able to. I’ve turned SSL on and off, made things a horrible mix of HTTPS and plain HTTP, switched the permalink to random weird things…

Jetpack keeps working through all of it.

SO… I’m impressed: when jetpack works, it works really well. I think it is abundantly clear that it is not Jetpack that needs fixing.

But ooh, boy when it doesn’t work… I’m sure it’s some little setting that is wrong somewhere that is making the other two sites fail, but I really can’t figure out what.

I do wish your “debug” site was just a tiny bit more verbose and less “friendly” – show me the headers and the responses, pelase give me at least something to look at besides “unexpected error”: that’s a debug site, it shouldn’t try to be “low tech”.

It wasn’t so much that you could do anything, but a distant hope that maybe you had notes from other people and could say “try looking at these things in .htaccess” or “go check somethingorother.php in wp_randomfolder and make sure it doesn’t have a set_value(“hate_jetpack”, “true”)”

I’ll see if Verio will do anything other than give me a small canned response about upgrading to premium support… not feeling hopeful there.

• This reply was modified 3 years, 4 months ago by foxfireforge.

Another update. I got them to tell me where the access log is, and I’m looking at it.

192.0.85.88 - - [27/Oct/2021:12:57:12 -0400] "POST /xmlrpc.php?<redacted> HTTP/1.1" 200 132 "https://ffforge-tx.com/xmlrpc.php?<redacted>" "Jetpack by WordPress.com"
192.0.85.88 - - [27/Oct/2021:12:57:14 -0400] "POST /xmlrpc.php?<redacted> HTTP/1.1" 200 323 "https://ffforge-tx.com/xmlrpc.php?<redacted>" "Jetpack by WordPress.com"
192.0.85.88 - - [27/Oct/2021:12:57:21 -0400] "POST /xmlrpc.php?<redacted> HTTP/1.1" 200 899 "https://ffforge-tx.com/xmlrpc.php?<redacted>" "Jetpack by WordPress.com"

All three of those were generated by putting “https://fenric.com/” in the Jetpack Debug page. I’ve tried a few more times and no matter which of my three sites I put in the debug page, the access log shows the attempt going to ffforge-tx.com, but of course only the ones that are actually supposed to be going there actually work.

So… now I think at least I see what’s going on. Somehow, regardless of which domain was asked for, Apache is always serving the copy from ffforge-tx.com (the most recently created sub-site). If you have any notion at all what this means I should tell the very unhelpful Verio support people, I’d really appreciate the hint.

• This reply was modified 3 years, 4 months ago by foxfireforge.

So, in the ongoing opera of strangeness…

I tried downgrading my PHP version to 7.3 through Verio’s console, and that got fenric.com to connect. Unfortunately, it broke the other two sites as it appears something in the WooCommerce suite needs 7.4. I put the PHP version back to 7.4, and that immediately broke fenric.com’s jetpack connection again.

Hi @foxfireforge,

Thanks a lot for the thorough updates. From what you shared, it looks like the issues you’re having aren’t related to Jetpack itself, but more to the servers settings you have in place.

I’d recommend keeping the folks at Verio at work on that, to understand where the root of the issue is. Once we know that, and a fix will be in place from Verio, we can check the site(s) with our debug tool to see if everything is well connected.

Thanks for keeping us updated on that!