Hi @gwalliman,
Thanks for reaching out, and good job updating everything—that rules out a common cause.
We’ve found that the site is still partially registered as 127.0.0.1 on our end. While the siteurl and home values are now set correctly to https://ddlegio.com, the main domain value is still showing as 127.0.0.1.
Before we move forward with a full reset, could you please confirm: What is the correct, intended live URL for your site? Is it https://ddlegio.com, or something else?
Once we confirm that, we’ll be able to assist further.
Hello, yes that’s the intended domain, https://ddlegio.com.
Thank you!
Hi @gwalliman,
Thanks again for confirming the intended domain is https://ddlegio.com.
From what I can see, even though the domain is correct, your site’s siteurl and home values still appear to be set to http://127.0.0.1/wp. Could you please check the Settings > General page in your WordPress dashboard and confirm that both the WordPress Address (URL) and Site Address (URL) are set to https://ddlegio.com?
Also, it looks like your site’s xmlrpc.php file isn’t accessible right now—it returns a “Not Found” error when visiting https://ddlegio.com/xmlrpc.php. Jetpack relies on this file to connect properly, so you’ll want to make sure it exists and isn’t blocked or removed.
Once you’ve updated the URLs and ensured xmlrpc.php is reachable, let us know and we’ll be happy to continue troubleshooting the connection.
Looking forward to your update!
Howdy – I just updated the siteurl and home values, so that should be good.
Regarding xmlrpc.php, we have our site set up such that wordpress core files are installed in a subdirectory (/wp/), so you can find xmlrpc.php at https://ddlegio.com/wp/xmlrpc.php. This construction is a legacy of the service we’re using to host the site.
Is there a way for us to configure Jetpack to run with this setup? Alternatively, could we somehow symlink /xmlrpc.php to point to /wp/xmlrpc.php – would that even work, and if it would, how would you recommend we do that?
Hi there, @gwalliman,
Thanks for making the changes at your end – I made some changes at ours as well to reflect the xmlrpc URL to our servers.
I still see some errors (mainly error 405) as Jetpack attempts to connect. There are a few things you can try to re-establish a working connection:
- Ensure our IP range is fully in the allow list at your end: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/
- I see you’re using Cloudflare currently. Can you please make sure that you’ve followed the following guides, which outline the proper setup for Jetpack and Cloudflare?
- check for other any security/caching plugins you may have enabled, and try temporarily disabling them to see if it fixes the problem.
- you may also want to search for any firewall on your server-side that might be blocking the communication with the xmlrpc.php file – your host should be able to help you with that.
I know it’s a bit of a long list, but that covers a good range of causes we can fix 🙂 🤞
Let us know what you find out!
Hi there, @gwalliman,
Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
Hello, apologies for the delay in my response.
I’ve applied some of the changes described in the articles you linked. When I do a test POST request to https://ddlegio.com/wp/xmlrpc.php, I don’t get blocked, so I hope this means that things should work now? Please let me know if you continue to get errors on your end.
Hello @gwalliman – the XML-RPC looks good now but I see the site is not connected with Jetpack, so could you please reconnect the site to Jetpack and let us know? After that, we will check again.
Looking forward to your reply!
Hate to say it but I’m still getting the 500 error in the console / “An error occurred. Please try again.” message.
Any further ideas?
Hi @gwalliman –
I made another adjustment on our end that may fix the issue. Could you try the uninstall/reinstall cycle again?
Still getting the same error @lastsplash
I’m deactivating / reactivating the plugin between each test. Should I be trying anything else?
Hi there, @gwalliman,
Thanks for trying our suggestions – I checked the connection and I can see a different error now. That doesn’t mean we are not making any progress: a different error means that we can use a different solution to fix the connection 🙂
There is still something blocking the xmlrpc.php connection, causing Jetpack to disconnect.
I’d suggest checking again some of the bits we already mentioned – considering the new error something might have changed meanwhile – eg if you have any security plugins activated that might be blocking our requests. If not, try contacting your hosting provider again, and asking them to check their security logs to see if they are blocking or otherwise limiting incoming and outgoing connections over XML-RPC.
Our requests look like the following:
Please ask them to allowlist the IP addresses listed above. Note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage allowing specific IPs, although with some hosts it may be the only option.
Please note that many of the errors we are seeing (like 404, 403,, 405 etc) are 100% server related, so we need your host to find the root of the issue on their settings and adjust it 🙂
Hope that’s all clear! Let us know how that goes and thanks for sorting this out with us!
Thank you for the info. I’ve sent a tech support request to our hosting provider.
Note that when I try to hit https://ddlegio.com/wp/xmlrpc.php directly through Postman with either a GET or a POST, I don’t get any server errors. I don’t get useful responses because these aren’t the correct ways to call xmlrpc, but it does let me through. Any idea why I can hit the URL directly, but Jetpack can’t?
Hi @gwalliman,
You’re right, you can access /wp/xmlrpc.php directly through Postman because you’re specifically targeting that file.
However, Jetpack always tries to connect to https://yourdomain.com/xmlrpc.php (the site root) automatically, based on your site’s public URL.
In your case, because WordPress is installed inside /wp/, there’s no xmlrpc.php file at the root of your site (https://ddlegio.com/xmlrpc.php), and that’s why Jetpack’s connection fails with a “Page not found” error.
To fix this cleanly, there are two options:
- Set up a server-side redirect from
https://ddlegio.com/xmlrpc.php to https://ddlegio.com/wp/xmlrpc.php.
This is a simple and safe fix that avoids modifying any WordPress files directly. Your hosting provider should be able to help with setting up this redirect.
- Alternatively, you can copy the
xmlrpc.php file from the /wp/ folder to your site’s root and adjust it slightly to load WordPress from the correct location. If you prefer this option, we recommend asking your host or a developer to help, since it involves a small code adjustment.
This small change would help Jetpack and other services that rely on XML-RPC find your site correctly, and it’ll future-proof things in case you use any additional plugins or tools that depend on it down the line.
Let us know which option you’d prefer, and we’ll be ready to continue from there!
-
This reply was modified 1 year, 1 month ago by
Alin (a11n).
Hello @gwalliman,
I’m just following up to check if you have any updates on the above. Look forward to your updates.
