Can’t connect

Please, can anyone help? The error log is so generic… that it does not help me track the cause at all 🙁

my hosting says that CML-RPC are blocked by default and will never be allowed by them in any case…

Hello, ciao!

I ran numerous random tests and I am quite desperate… I even tried another plugin (paid) that does a similar thing… and I dislike it so much. Jetpack is so simple to use, and has a nice interface, i so much want it to work… but the hosting team wasn’t really helpful.

I ran several diagnostics on my side:

1. Hosting / XML-RPC / allowlist

I asked my hosting provider, Tophost, about XML-RPC. They confirmed that XML-RPC requests are blocked on their servers and that they do not enable them.

They did not offer a way to allowlist Jetpack/WordPress.com requests or enable XML-RPC just for this site.

I also tested this directly.

GET https://www.agedonazionale.org/xmlrpc.php

returns the expected message:

XML-RPC server accepts POST requests only.

But a POST request to the same file:

curl -i -X POST https://www.agedonazionale.org/xmlrpc.php

returns:

HTTP/2 401
Errore 401 - Richiesta autorizzazione

The same happens with a valid XML-RPC body:

curl -i -X POST https://www.agedonazionale.org/xmlrpc.php \
-H "Content-Type: text/xml" \
--data '<?xml version="1.0"?><methodCall><methodName>system.listMethods</methodName><params></params></methodCall>'

This also returns HTTP/2 401.

So XML-RPC POST requests are blocked at hosting/server level before WordPress can handle them.

2. Security / cache plugins

I temporarily disabled the cache-related plugins and retried the Jetpack Social connection.

The result did not change.

The failing request still returns:

500 Internal Server Error

with:

{
  "code": "jp_connection_update_failed",
  "message": "Something went wrong while creating a connection.",
  "data": "Could not update the Jetpack Social connections on the remote Jetpack site. No Jetpack Social connection created."
}

I also checked WordPress Site Health. There are no critical issues reported. The only recommendations are inactive plugins/themes, missing optional Imagick module, and one failed SeedProd scheduled event.

3. REST API / alternate method

The REST API is reachable, and POST requests are not generally blocked.

For example:

curl -i -X POST https://www.agedonazionale.org/wp-json/wpcom/v2/publicize/connections

returns a normal WordPress/Jetpack REST JSON response about the missing keyring_connection_ID.

Another REST test:

curl -i -X POST https://www.agedonazionale.org/wp-json/jetpack/v4/connection/test

returns a normal WordPress REST JSON response:

rest_no_route

So REST API POST requests are not blocked in general.

When I try to connect Facebook through Jetpack Social, the Facebook OAuth step seems to work: I can see the list of my Facebook pages.

The failure happens after that, when Jetpack Social tries to create/save the connection.

In Chrome DevTools → Network, the failing request is:

POST https://www.agedonazionale.org/wp-json/wpcom/v2/publicize/connections/?_locale=user

It returns:

500 Internal Server Error

Response body:

{
  "code": "jp_connection_update_failed",
  "message": "Something went wrong while creating a connection.",
  "data": "Could not update the Jetpack Social connections on the remote Jetpack site. No Jetpack Social connection created."
}

The request payload seems to be present and valid. It includes:

external_user_ID
keyring_connection_ID
shared: true

4. Site accessibility / Jetpack connection

The site is publicly accessible and is not behind password protection or maintenance mode.

In Jetpack, the connection appears to be OK:

Site and account connected
Everything looks good
Connected as owner: Admin

Server shows

REMOTE_ADDR = a short internal ip
HTTP_X_FORWARDED_PROTO = https
HTTP_X_FORWARDED_FOR = a different ip

I do not see particular issues with firewall, but I might be wrong.

WordPress marks the website is in a reverse proxy.

Given all this, the issue seems to be specifically that Jetpack Social receives the Facebook connection data but cannot update the Jetpack Social connections on the remote Jetpack site.

Could you please check on your side why this remote Jetpack Social connection update is failing?

Also, can you confirm whether Jetpack Social can work on this site without XML-RPC, using the alternate connection method you mentioned? Or does Jetpack Social still require XML-RPC at some point in the connection/sync process?

At this point I need to know whether this can be fixed on the Jetpack connection side, or whether Jetpack Social simply cannot work on this hosting because XML-RPC POST requests are blocked at server level.

Thank you. Grazie mille!