WordPress.com Shows Two Sites Connected When Only One Is

Found two versions of the same site on debugging page:
https://prnt.sc/NfHcRqTx8RcA

Hi there

I have removed the duplicate site connection, but there is still an issue with the xmlrpc file, which seems to be a Sucuri/Cloudproxy block.

Try deactivating Sucuri and any other security plugins and then try to reconnect Jetpack.

@drawmyface thx for the duplicate removed and was also informed by GoDaddy XMLRPC is not supported on 8.0PHP and suggested to downgrade to 7.4PHP. The email is copied below for bug purposes just in case it could be resolved by WP. I burn candles from both ends ??

From GoDaddy:
“`Regarding the issue you experienced with XML-RPC, this module isn’t installed and supported by default with the latest PHP versions (8+) and this is why you’re seeing the error. I’m afraid that since this module is no longer maintained, we will not enable it for the time being.

The reason for this decision is that the module is relying on abandoned projects and we can’t confirm it’ll work as expected or that it’ll remain secure. We reached out to our engineers to ask them about enabling the module, but at the moment we’re gauging the impact the lack of this module has on sites. If this plugin is required for your online shop to work as expected, I would recommend either:

a) Consult with the developers to see if there is another solution to consider.
b) downgrade to PHP 7.4 because XML-RPC is installed by default in that version.
c) or transfer your site to a different plan that allows you more control over the PHP modules installed on the server.”

Im forced to downgrade PHP version until a patch for the new PHPs are available. Let me know if you need info for GD reply.

• This reply was modified 1 year, 11 months ago by kingbrown75.

Hi @kingbrown75

Sorry for the confusion here. While Jetpack uses xmlrpc.php, it doesn’t need the XMLRPC PHP module, as WordPress provides its own xmlrpc server.

It does need the XML module, but that should still be enabled by default in PHP 8.0.

The error respose we are seeing is HTTP/1.1 429 Denied for too many attempts

Can you check with GoDaddy if they have any rate limiting in place that would cause this error?

Hello @kingbrown75,

It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!l

Hello again, I don’t know if this is related to whatever you fixed or a new ticket. My phone is not getting the verification code after many one minute attempts. The last two numbers of the phone number are correct in the confirmation.

Message sent to phone number ending in 83

https://prnt.sc/HCbpL-7ZAHxd

Hi @kingbrown75 –

Please follow the directions here for assistance with account access:

https://wordpress.com/support/account-recovery/#account-recovery-form

Hello, sorry to bother anyone but the link provided is not helpful. The password was reset but the issue is with the two-step authentication. My email and cell are registered but am not getting the sms code or an email from WP. There are no links or options to send code via email https://wordpress.com/support/account-recovery/#recovery-email-and-sms-number

Hi @kingbrown75 –

Within that document, there is a link to a form for assistance with account recovery.

Please fill out the form for assistance. We can’t help with account access via the forums.

Hello, the original problem still exists with the XMLRPC issue. The firewall setting was changed some time back to allow XMLRPC https://prnt.sc/yyQKI-rtYh7_.

WordPress.com still shows error messege “XML-RPC is not responding correctly ( 429 )” even though my website/xmlrpc.php shows no issue https://prnt.sc/pan9PtqqhN-0.

JetPack was reinstalled after totally deleting from the production and staging sites where now WordPress.com doesn’t register the new installation. https://prnt.sc/P_sLP3i3cu2T but WooCommerce shows no issues https://prnt.sc/PmZsy2FT9Il-.

The only thing noticable on WordPress.com, that was not screenshot, was the XMLRPC issue only occurred on the production site but not the staging site.

WordPress.com connected to the website but still showing the same issues. https://prnt.sc/9cJ36j4xlShE / https://prnt.sc/Y2ppgwAnya-H

• This reply was modified 1 year, 10 months ago by kingbrown75.

Another observation is getting a 500 error when reinstalling JP having to do a hard refresh ctrl+F5 to finish the installation.

Hi there,

That was the right change to make to your GoDaddy firewall settings to unblock XML-RPC. I’ve just run diagnostics, and the connection looks good from my end.

Are you still encountering issues?

Yes, I don’t know if to create a new ticket but the issues evolved after reinstalling JP trying to fix the XMLRPC issue. Now there are new issues I don’t know how to explain but have screenshots and waited a few days to see if it fixes itself. see screenshots

https://prnt.sc/n0AJQTaVAxEh

https://prnt.sc/FZY6g7Nnrn82

https://prnt.sc/5_SqB_h4SICz

https://prnt.sc/sfEj99eEbQpS

https://prnt.sc/XlaeML4h7Ox7

https://prnt.sc/V4JiZVSyPH-1

https://prnt.sc/NDRKgnhl-qPN

Now a plugin conflict test was done removing all but WC & JP then tried reinstalling JP getting this message https://prnt.sc/hiLueJKOE156.

https://prnt.sc/sdy8ZtGVg6YU