Error Details: Unable to insert blog.

Hi there!

It looks like there’s a problem with the XML RPC endpoint on your site.
Problems accessing XML RPC could be due to another plugin, a security module, or a block on your server. As a first step to fixing this, I’d recommend contacting your host to see whether they block XML RPC and if so, to unblock it for Jetpack (they can find our IP range here https://jetpack.com/support/hosting-faq/).
Let us know what you hear back from your host, and we’ll retest the Jetpack connection once ready.

I am the host and we are not blocking XMLRPC: https://giep.nc/__/core/xmlrpc.php

The logs:

192.0.112.85 - - [09/Sep/2020:09:58:59 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.112.85 - - [09/Sep/2020:09:59:00 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.118.113 - - [09/Sep/2020:09:59:04 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.118.113 - - [09/Sep/2020:09:59:05 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.112.116 - - [09/Sep/2020:09:59:16 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.112.116 - - [09/Sep/2020:09:59:18 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.118.208 - - [09/Sep/2020:09:59:21 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 207 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"
192.0.118.208 - - [09/Sep/2020:09:59:23 +1100] "POST /__/core/xmlrpc.php?for=jetpack HTTP/1.1" 200 169 "https://giep.nc/__/core/xmlrpc.php?for=jetpack" "Jetpack by WordPress.com"

It works with an other website with standard directory layout on same host.

• This reply was modified 4 years, 2 months ago by Lox.

The next thing I would rule out is a plugin conflict as @fresatomica mentioned.

I disabled all extension but jetpack and akismet: same issue

I suspect it is related to having copies of it: one for development, one for staging and one public. What happened following the 8.9 update is that the public website told that it was a copy of staging and since then it is not possible to connect jetpack on all version.

I have been checking the info in the Debugger and, from the errors I see there, it seems that the SSL certificate may not be properly configured:

http_request_failed: cURL error 60: SSL: no alternative certificate subject name matches target host name 'dev.giep.nc'

Since you’re self-hosting your site, you may want to have a look and that and make sure all is correct there.

So it is related to the old staging version (dev.giep.nc) which doesn’t hold any wordpress since a while, the new staging version is staging.giep.nc.

It started like so: after updating to 8.9 Jetpack first told me on the production version that it was a copy of the staging version. Then no way to connect back to JetPack and fix it. But https://giep.nc has a proper SSL certificate.

The string “dev.giep.nc” is nowhere to be found in the database or in any file of giep.nc.

Don’t you have it wrong on your side, why are you connecting to dev.giep.nc the jetpack activation request comes form giep.nc ?

• This reply was modified 4 years, 2 months ago by Lox.

Ah ok, I see that now.

Please try deleting Jetpack specifically from the Plugins section of your blog’s Dashboard: https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

This will clear out Jetpack’s settings, and it should work properly after a reinstall.

I already tried it, I even tried deleting manually all wp_options and transients containing “jetpack” in their key name. I have just done it again, the issue is still there.

Prior of that, I resurrected dev.giep.nc with a 301 redirect that keeps request_uri. It doesn’t help.

The question is what is making Jetpack servers reply to a different hostname than the one that requested the activation ? Don’t you have that value stored together with the data that permits to detect duplicated websites ?
Can you try deleting it manually please ?

I had the same problem on another website, but as a precaution I just tried to activate Jetpack again and it worked this time.

For another one I lost the jetpack connection the same way and could not activate it anymore. I added “www” and could activate it. Which is weird.

I have tried an extension free, fresh installation of WordPress with the same specific directory layout: activation of Jetpack went smooth so it is unrelated to that specificity.

The question is what is making Jetpack servers reply to a different hostname than the one that requested the activation ? Don’t you have that value stored together with the data that permits to detect duplicated websites ?

That URL is actually in your settings:

domain: giep.nc 
siteurl: https://dev.giep.nc/__/core 
home: https://dev.giep.nc

Make sure you have updated that to the correct URLs and we’ll retest the connection.

If it was true, I wouldn’t be able to login and administrate because of automatic redirects.

As I said dev.giep.nc is nowhere to been seen. I searched in all tables, and in all files using grep.

MariaDB [(none)]> use giep_site
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [giep_site]> SELECT * FROM <code>wp_options</code> WHERE <code>option_value</code> LIKE '%dev.giep.nc%';
Empty set (0.02 sec)

MariaDB [giep_site]> SELECT * FROM wp_options WHERE option_name LIKE 'siteurl' ;
+-----------+-------------+-------------------------+----------+
| option_id | option_name | option_value            | autoload |
+-----------+-------------+-------------------------+----------+
|         1 | siteurl     | https://giep.nc/__/core | yes      |
+-----------+-------------+-------------------------+----------+
1 row in set (0.00 sec)

MariaDB [giep_site]> SELECT * FROM wp_options WHERE option_name LIKE 'home';
+-----------+-------------+-----------------+----------+
| option_id | option_name | option_value    | autoload |
+-----------+-------------+-----------------+----------+
|         2 | home        | https://giep.nc | yes      |
+-----------+-------------+-----------------+----------+
1 row in set (0.01 sec)

• This reply was modified 4 years, 2 months ago by Lox.

Ok, please reach out via https://jetpack.com/contact-support/?hpi=1 so we can take a closer look.