glonojake
Forum Replies Created
-
This seems to be fixed now by setting the new setting “Prevent caching URLs without a trailing slash (/)” to No! Thanks so much!
Awesome! Thanks!
Thank you! I will take look at those things!
Thank you!
The javascript errors revealed a new cloudflare security rules was overly aggressively blocking assets in wp-includes. I fixed that rule and the issue went away. Thank you so much for leading me in that direction!
I can no longer recreate the issue. I will ask my editor if he can check for JavaScript error messages.
Update: Re-enabled all my plugins and everything seems back to normal for me. However, it’s the same for my editor. He still has the blank, uneditable textarea where he should see the existing post. And logging in from an incognito browser doesn’t fix it, so it be something stored somewhere in the WP db, right?
I am on standard theme: Twenty Twenty-Five Version: 1.4.
I disabled all plugins and I can edit in the Block Editor. I enabled the Classic Editor plugin and I can edit in Classic Editor now but it looks weird and the Visual/Code toggle does nothing.
Yes, confirmed, although I still don’t understand why it uses Jetpack’s CDN for related post images if I don’t have “Speed up image load times” enabled. But whatever, that’s fine. It works. Maybe I should enable site accelerator after all!
Okay I see. So you are not hitting that from one of Jetpack’s IP addresses. I think I’m all set now though. I whitelisted Jetpack’s IP addresses and things seem to be working fine…at least until I hit my resource limit and start throwing 508s.
Thank you for all your help with diagnosing the issue!
When I follow that link I see the following response:
XML-RPC server accepts POST requests only.Is that not what you’re expecting? What is the expected response?
I have a cloudflare rule for ip.src in {192.0.64.0/18} to skip all other rules.
- This reply was modified 6 months, 2 weeks ago by glonojake.
Thank you. I have whitelisted Jetpack’s IPs and I’m engaged in the whack-a-mole of blocking bad actors.
I wonder why Jetpack’s Photon user agent is constantly scraping my image folder?
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.
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.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.