Related Posts images not showing
-
Looks like it’s trying to find my images on wp’s cdn but I don’t have that enabled. How can I prevent this from doing that? Also, I have to re-enable “Jetpack blocks” in my settings at least once a week. No sure if it’s related, but it’s annoying.
The page I need help with: [log in to see the link]
-
Hello there, Sebastian here, I hope you are doing well.
Thank you for reaching out and sharing your concern with us.
I can see an error with the connection between your site and Jetpack. Jetpack needs this connection to function correctly for most of its features. This could be related to the issue with the Jetpack blocks.
I notice that your site is using Cloudflare. While Cloudflare and Jetpack usually work well together, sometimes certain settings can block Jetpack from connecting properly. To move forward, could you please double-check that Cloudflare is configured using these instructions:It’s also important to make sure our IP addresses are allowlisted:
Alternatively, you could choose to temporarily disable Cloudflare:
Once you’ve had a chance to adjust those Cloudflare settings, let us know—we’ll be here to recheck your site’s connection and help make sure everything runs as expected.
Regarding the CDN images, could you check if you have deactivated the Site Accelerator as described here:
I hope this helps; please let us know how it goes.
Cheers,
Thank you. I think I may have been blocking Jetpack IP addresses (192.0.0.0/15) because it looked like they had been hammering my site and I didn’t know what they were. (A.I. scrapers have been using up all my resources so I’ve been aggressively trying to block them.) I was also rate-limiting xmlrpc.php.
I removed the Jetpack IPs from my block rule and added the following to my “skip” rule: (ip.src in {192.0.64.0/18}). And I also removed the rate-limit on xmlrpc.php.
Also, I confirmed I have a page rule set up for https://gloriousnoise.com/wp-admin/* to Disable Security, Browser Cache TTL: 4 hours, Cache Level: Bypass, Disable Apps, Disable Performance.Hello there, thanks for following up on this issue.
I reviewed the connection, but I still cannot see access to the XML-RPC.hpp file is blocked:
https://gloriousnoise.com/xmlrpc.php?for=jetpack
You can also check our debugger tool showing this error:
https://jptools.wordpress.com/debug/?url=https%3A%2F%2Fgloriousnoise.com
Please make sure that you allowlist our IP address on Cloudflare as mentioned here: https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/#allowlist-jetpack-ips-in-cloudflare-settings
You can find the whole list our IPs list here: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/#using-jetpack-with-cloudflare-and-or-sucuri
Please let us know how it goes.
Warm regards,
Oh jeez I had a rule in my .htaccess file. I removed it and now this tells me everything looks great:
https://jptools.wordpress.com/debug/?url=https%3A%2F%2Fgloriousnoise.com
Sorry to be a dope.Hi there, @glonojake,
Please don’t apologise – we’re here to help, and we see how an extra rule could be set in the .htaccess file: better safe than sorry, right? 🙂
That said, I checked the Jetpack connection, and it appears to be broken again. If you saw it working fine (with the green icon), it means that you might be experiencing some intermitting hiccups.
The error I see is related to some resources limits your site have exhausted:
The website is temporarily unable to service your request as it exceeded resource limitI recommend reporting this to your hosting provider, as they should be able to address it for you.
Let us know when that’s done, and we’ll be happy to test the connection again 🙂
I’m on shared hosting so resource limits are a constant bane of my existence. And the original reason I blocked access to xmlrpc.php is because it was being hammered. Somehow I need to figure out how to limit bad actors from using up all my resources but still allow legitimate traffic. Which, of course, is way harder in the age of a.i.
Hi @glonojake,
Thanks for the update and for sharing a bit more about your setup. I completely understand how frustrating it can be to balance resource limits with keeping legitimate traffic flowing. Shared hosting can definitely make this tricky, especially with high‑frequency requests hitting
xmlrpc.php.A few things to consider – and apologies if we have already mentioned some!
- Allow Jetpack and legitimate traffic: Jetpack needs access to
xmlrpc.phpto communicate with WordPress.com. Temporarily blocking it (even with good intentions) will continue to break features like Related Posts or Stats.
One option is to whitelist Jetpack’s IP ranges rather than opening everything. Jetpack publishes a list here: https://jetpack.com/support/hosting-faq/#jetpack-ip-addresses
- Rate limiting / blocking bad actors: some security plugins or hosting firewalls let you limit repeated requests to
xmlrpc.phpwhile still allowing whitelisted IPs. You can try this out as this can reduce resource abuse while keeping Jetpack functional.
- Monitor traffic patterns: Cloudflare can help filter automated bots, and some shared hosts provide traffic analytics to help you spot abusive requests.
I realise this doesn’t solve the shared hosting resource limitation entirely, but whitelisting Jetpack and selectively rate-limiting requests is usually the safest way to keep Jetpack connected without fully exposing your site to spammy hits.
Let us know if this is something you can (re)try out, and if you can, let us know how it goes. Thanks!
- Allow Jetpack and legitimate traffic: Jetpack needs access to
You must be logged in to reply to this topic.
