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.
Thread Starter
akeslo
(@akeslo)
Hi James
Thank you for the help! I have given this a try but unfortunately running into the same error. I uninstalled via the admin portal.
I’m seeing now that the Jetpack debug is showing: “Can not resolve your domain “A record”. I moved the domain over 24+ hours ago but still under the 48 hour mark.
-
This reply was modified 5 years, 11 months ago by
akeslo.
Thread Starter
akeslo
(@akeslo)
@macmanx I’m convinced there is some kind of issues on the jetpack end, anything else you’d recommend trying?
Thanks.
I’m still seeing that same error on your site. Have you already tried reaching out to your hosting provider, as indicated in the error message in the debugger?
Thread Starter
akeslo
(@akeslo)
@fresatomica This is a VPS so I have full control over DNS. I have a valid A record which can be seen here: https://dnschecker.org/#A/behindtheracquet.com
Not sure why the jetpack debugger is reporting it cannot find the A record.
I had a closer look and it seems we’re being blocked from accessing https://behindtheracquet.com/xmlrpc.php which Jetpack requires to function.
Unfortunately, blocking XML-RPC is not a great solution for fighting security risks. It’s akin to selling your car because you don’t want it to be stolen.
Your site’s XML-RPC file is kind of like a communication gateway to your site. Jetpack, the WordPress Mobile Apps, and other plugins and services will use this file to communicate to your site. If this is blocked, you will have other issues pop-up down the road for the same reasons.
If you are using any security plugins, please try connecting with those temporarily deactivated. If you don’t have any, or if that didn’t work, I would suggest contacting your hosting provider and asking them to unblock your site’s XML-RPC. The most popular hosting providers out there have managed to find other ways to protect their servers without having to hinder your site and your ability to use services with your WordPress site.
Thread Starter
akeslo
(@akeslo)
Hi @fresatomica,
Thank you. I am using a subdirectory which
puts my xmlrpc here: https://behindtheracquet.com/wp/xmlrpc.php
Does this change anything? How do I have jetpack point here? This worked previously, thanks.
Oh, actually, the URLs you set for your site is probably what’s causing the issue. It seems that your site’s URL is https://behindtheracquet.com, however, you have set it to be https://btr.akeslo.com.
You’ll want to change the URL settings so they all match. Let me know if that helps.
Thread Starter
akeslo
(@akeslo)
Hi @fresatomica
Thank you – where do I change this? I’m seeing the proper url under settings in my wordpress dashbaord as well as in the db. BTR.akeslo.com was the name i used while testing.
View post on imgur.com
Hmm. Jetpack isn’t connecting properly still. Have you removed the Jetpack plugin and then re enabled it already? Can you let me know once that’s been done and I will check the connection once more.
This may be a plugin or theme conflict. As a next step, Please attempt to disable all plugins, and switch to the default Twenty Twenty theme. If the problem goes away, enable them one by one to identify the source of the problem.
If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.
Thread Starter
akeslo
(@akeslo)
@lizkarkoski Thank you
I had tried the above multiple times without luck:
– Disabled all plugins
– Reverted to Twenty Twenty Theme
This was all done via Health Check.
I am still unable to connect with the same error message: “Unable to insert blog. Please try again or contact support.”
@akeslo I have updated the site settings on my end. Could you please test this again?
Thread Starter
akeslo
(@akeslo)
@fresatomica This is working now, thank you so much!
Awesome, thank you for letting me know! 🙂
