When I try to set-up Jetpack Boost, I get an error message:
Failed to connect to WordPress.com
HTTP 404 error received while communicating with the server.
I am having a look at your site’s connection to Jetpack in the background and I am seeing that it is connecting correctly without any issues at the moment.
Have you made any adjustments on your side to take care of the connection issue?
If the connection issue is still there from your side, please share what you are seeing from us through screenshots. You can follow our guide here on how to make screenshots: https://wordpress.com/support/make-a-screenshot/
in the meantime, I did a fresh new install of Jetpack and Boost. Now, I get that message:
When I click “Verwalten“ (Manage) and choose the free option, it starts loading and loading and loading without an end. By the way, like my Jetpack stats.
Thanks for your help!
PS: In the meantime, my site is connected to WordPress.com!
This reply was modified 1 year, 3 months ago by Setzfehler.
Thanks for the extra information. I ran more connection tests, particularly on your site’s XML-RPC endpoint, which Jetpack relies on to communicate with your site, and only on occasion did I get the expected 200 OK responses.
In most cases, it was a 503 Service Unavailable response, and the last test request sent to your server resulted in a 502 Bad Gateway response. For more information, here are brief descriptions of those HTTP statuses:
503 Service Unavailable: The server is currently unable to handle the request due to maintenance or overload, and the client should try again later.
502 Bad Gateway: The server acting as a gateway or proxy received an invalid response from the upstream server it accessed in attempting to fulfill the request.
This is something your hosting provider should be able to provide insight on. If you don’t have any security plugins that could be blocking or rate-limiting our requests, please try contacting your hosting provider 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:
File: http-//your-site.com/xmlrpc.php (excluded your site URL here for privacy reasons)
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.
thank you for your answer even I do not think that this is a hosting provider side issue. I am running another site there without having any problems with Jetpack (by the way: If they work, the new Jetpack stats are very useful–many thanks to your developers!) and Boost.
But I remembered that I was manually disabling XML-RPC a while ago because of security reasons. I enabled it again but that didn’t help either.
I apologize for my delayed response. After checking the website you provided above, https://ronaldfilkas.de/, it seems that the Jetpack connection issue has been resolved. Great job!
If you’re still experiencing any problems with Jetpack Boost or need any further assistance, please don’t hesitate to reach out to us. We’re always here to help in any way we can.
I am mostly using Ubuntu Linux, and the newest browser version. But as I mentioned a couple of times before, I am running another WordPress site where everything (Jetpack stats and Boost) works within same OS and browser. So, the problem must be caused by something within this special site. The only way to see my stats is to login to wordpress.com but no way to start Boost.
Could you test by just having the Jeptpack and Jetpack Boost plugins active, and the others deactivated? If it works, then reactivate the other plugins one by one to see which one might be causing a conflict. Thanks.
yes, I tried that already by using the Health Check & Troubleshooting plugin. No positive results to tell. As someone else from support team suggested, I will try disconnecting, deleting, re-installing, and re-connecting Jetpack to WordPress.com again.
I looked through some previous support history for your domain (in our internal records) and it looks like you worked with us a few years ago on something for a subdomain for this site. Maybe this is the other site you’re referring to as working well here?
I took a look and compared the settings between the two sites, and it looks like the one that is working well with both the Jetpack connection and Jetpack Boost has WP_MAX_MEMORY_LIMIT set to 768M. The site you’re having trouble with is set to 256M. Can you bump that up, and see if it makes a difference?
