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.

Tag:-

26 comments.

  1. Lion

    same here

  2. Neil

    come on facebook WTF

  3. Xavier

    Same problem.Are you on WP with Wordfence Plugin ?

  4. 妹尾 みどり

    same here

  5. Joe

    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.

    1. Joe

      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.

  6. József

    Hi, Did you manage to find a solution to the above mentioned error? This issue also affected a website I manage. The server firewall blocks requests as it retrieves data from links every second.

  7. Federico

    I'm reading all thread but still have the same problem here https://www.fondoposte.it/ Can anyone help me please?

  8. Brent

    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.

  9. Massimo

    Read this thread https://developers.facebook.com/support/bugs/1085796049211789/

  10. Xavier

    Same problem.Are you on WP with Wordfence Plugin ?

    1. Xavier

      Same problem.Are you on WP with Wordfence Plugin ?

      1. Xavier

        Same problem.Are you on WP with Wordfence Plugin ?

    2. Xavier

      Same problem.Are you on WP with Wordfence Plugin ?

  11. Elvedin

    +1 Same issue with us as well

  12. Loic

    +1 Same problem

  13. Chong

    +1 Same problem

  14. Gavin

    +1 Same issue here too, for a couple of days now

  15. Ed

    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.

    1. Ed

      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.

      1. Ed

        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.

        1. Ed

          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.

    2. Ed

      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.

      1. Ed

        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.

    3. Ed

      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.

  16. Massimo

    Same issue here https://developers.facebook.com/community/threads/945101610321800/

    1. Massimo

      Same issue here https://developers.facebook.com/community/threads/945101610321800/

      1. Massimo

        Same issue here https://developers.facebook.com/community/threads/945101610321800/

    2. Massimo

      Same issue here https://developers.facebook.com/community/threads/945101610321800/

  17. TC

    Same issue same timeframe!

  18. Richard

    Plus 1. We are also experiencing this same issue.

Add a new comment.