- Community
- Question
Facebook debugger has recently been returning 403 errors for our pages. It was previously working and we never did any adjustments. The problem became prevalent February 28, 2024.
same here
Hello, I had resolved the issues and write the blog about resolution. I hope this will helps https://sobiztrend.com/facebook-url-returned-a-bad-http-response-code/
come on facebook WTF
Same problem.Are you on WP with Wordfence Plugin ?
We are having the same problem, specifically when setting the "User data deletion" URL for a Login app. What's really annoying is that this URL:
https://www.anitacameron.com/-/Home/privacy/
is rejected by Facebook, while this URL:
https://www.lasvegasbestrealestate.com/-/Home/privacy/
is accepted. Both URLs go into the same backend code, and have identical robots.txt files. WTF, Facebook, indeed.
The FB engine is obviously not able to handle robots.txt files in the best possible way, try to put allow:* in the FB section and invalidate the robots.txt with the batch inalidator (https://developers.facebook.com/tools/debug/sharing/batch/).
Facebook has apparently added an explanation now: This response code could be due to a robots.txt block. Please allowlist facebookexternalhit on your sites robots.txt config to utilize Facebook scraping
I have no blocks on facebookexternalhit on my site robots. but already allowed it, still same issue.
Read this thread https://developers.facebook.com/support/bugs/1085796049211789/
Same problem.Are you on WP with Wordfence Plugin ?
same problem
You use Wordfence plug-in on Wordpress ?
+1 Same issue with us as well
+1 Same problem
+1 Same problem
+1 Same issue here too, for a couple of days now
Same issue. We thought it might be Cloudflare WAF rules, but we created a Skip exception rule and so that was not it. We can replicate the user agent and we get a 200 with cURL request. All other open graph tools are able to fetch without issue.
Exactly the same problem. I thought I was going crazy already. It started with a supposed issue with the og:image on just one page. Was that the same issue you had?
Did you solve de issue? We have similar problem.
We still haven’t found a solution…
Same issue here https://developers.facebook.com/community/threads/945101610321800/
No chance we're going to get a quick resolution from this :(
No hope of being able to report to Facebook
Same issue same timeframe!
still not resolve.
Report here https://developers.facebook.com/support/bugs/1085796049211789/
Plus 1. We are also experiencing this same issue.
