Facebook - URL returned a bad HTTP response code

StackOverflow https://stackoverflow.com/questions/23066205

Question

For my website, www.mymoviematch.com, I cannot share any articles / pages on facebook due to facebook not scraping my site.

When I try the debugger, https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.mymoviematch.com%2Fpremiere%2F, it gives me "URL returned a bad HTTP response code", 404 error.

Meta tags and server response seem to be alright, so no idea what that might cause. I have read many similar problems, but cant find fix for mine... Can anyone help please?

Thanks

Was it helpful?

Solution 7

I have managed to fix my problem. The issue were the DNS records that were blocking the scraper. So if you have similar issue, check your DNS records. Thanks for help.

OTHER TIPS

The error is quite strange. The only thing that comes in my mind is that you apparantly use an incomplete url in the

<meta property="og:url" content="http://www.mymoviematch.com" />

tag. I think it should match the full URL.

I got the same problem and solved it by changing my DNS settings. Facebook uses IP V6 so you need to specify correct IP V6 in your AAAA record (not only IP V4).

I had a rule in my apache mod security in the way. Temporarily deactivating it helped me. An IPv6 record is not required. I have only IPv4 and it works.

This problem occurs due to IPV6 address. Facebook by default use IPV6 address if available. My VPS has IPV6 enabled.

To Solve this problem you have to enable iPv6 in All Ningx config files for each virtual host (if many sites hosted) to listen Any IPv6 address at port 80.

This will solve the issue with Facebook opengraph.

Alternatively, you can completely disable IPV6 address to solve this issue.

Take a look of your server's MOD SECURITY. It block some patterns. try to add this line in your vhosts. (yourdomain.com.ssl.conf)

<Directory "/home/username/public_html">
        .......
        .......
        SecRuleRemoveById 958291
</Directory>

Make sure to check the mod_security logs and find the exact sec ID. In my case I added secID 958291

The 'og:image' property should be explicitly provided.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top