Facebook url randomly unreachable - facebook

I'm sure anyone who has worked with Facebook has encountered the url unreachable problem with the comments plugin and alike.
I managed to get around this initially by making urls go to the facebook app page rather the hosted page, figuring facebook would be able to find itself, and ammended the url with a query string which could internally redirect them to right content. For example "app.facebook.com/myApp/?myAppP=videos&myAppId=0001" would first of all load the facebook app page then redirect the iframe to show the videos page and play video 0001.
This worked great at first but seems to have become a little unpredictable. I have a list of different videos, all of which use the same url except that the "myAppId" is different so the correct video is loaded. However whilst the "comments" and "like" plugins work fine for about a 1/3 of them, the other 2/3 show the "url unreachable". I can see no correlation between the urls that work and those that don't. It seems completely random, but it is always the same one that do and don't work.
This has got me completely stumped. Any ideas?

try to disable sandbox on app settings

Related

Facebook Sharer has suddenly stopped working for me

I have a LAMP website which allows users to share a graph on Facebook. It was woking fine until May 1st but now whenever I try to share, I just get a grey box.
My site was using sharer.php to do the sharing and giving as the url a document which would generate a single graph, and in it's og:image and og:image:url tags I put a url which points to some code which generates an 800 x 400 png of the same graph. If I copy either url into a browser, they render exactly what I would expect, but if I post the same url to the Sharing Debugger tool, it gives me a blank image.
I have noticed that although clicking the Scrape Again button usually calls the url which renders the image as a png, every now and then it does not, but there is no indication as to why and the Scraped URL page shows exactly the page I would expect with the correct og:image tags.
I have tried changing from using sharer.php to the FB.ui 'share' method, but this has not fixed the issue.
I have also tried asking in the Facebook Developer Community but have had no response. I even tried to raise a bug with Facebook, but it won't let me.
This is driving me nuts. I just don't understand why it has suddenly stopped working. Have I missed something or has Facebook changed anything in the Sharer functionality? Is there any other way to debug this ?
Update: After a lot of tinkering I have found out that this only affects my account, and it affects anything I share on Facebook, not just things from my own site. Furthermore, it's only the preview of the shared page which is not working. What actually gets posted to Facebook is the correct image. I have tried multiple PC's and multiple browsers and it always fails even if I switch off all anti-virus/anti-malware/firewalls etc. Bizarrely, if I share from my phone, it works!

Facebook Not Scraping URL Properly (Blocked URL) On Fresh URL's

I have started to experience a really strange problem with Facebook link scraping/caching which seems random in nature.
On brand new posts when I go to check: https://developers.facebook.com/tools/debug/ with my new URL I get a message saying 'Cannot scrape: URL blocked'
We have literally been sharing URL's to Facebook for YEARS with no problem whatsoever. All open graph tags are present and working fine.
What is really weird is if I just manually press the 'scrape again' button it grabs all the bits properly and says everything is fine. It's always just the first attempt.
I have also tried manually calling the scrap API instead of letting Facebook do it when someone shares the URL for the first time and still sometimes (not always) it returns empty (just 'id' and 'url' returned) indicating the URL was blocked.
What's going on here it's driving me mad? We are nowhere near our API limits if maybe that was the issue...
Why would it say blocked first go on the debug page then literally 2 seconds later you press 'scrape again' and it works fine.
Just to note sometimes when it says blocked it still shows maybe the image in the link preview but no title or description. It's like it's grabbed some tags but then given up. Very strange...
I have checked our access logs and I can see 'Facebot' accessing our site fine.
Hope someone can help, I am really hoping this is some weird Facebook bug as I can't see any change in our code base that would effect this.
Facebook does not return anything helpful when this happens even with the API. I have no way in contacting Facebook direct either. If we are somehow getting blocked I would love to know why and fix that issue. But it's impossible to debug at the moment.
Just to note I have 3 sites all running the same code base (WordPress environment). They are all experiencing this issue. All been running fine for many years.
Cheers
This was to do with rate limiting that was not visible in the Facebook APP dashboard. Helpful...
Full details here: https://developers.facebook.com/bugs/232343637174087/
Solution for your problem: You can use Facebook image button after adding link on Facebook news feed, like shown in iamge
second thing upload image on othe site and give the image path to your website and then put it on your news feed, you can get definitely positive result using this two methods.
also refer this image
thanks hope this two will work for your problem

og:image shows only after 4 share "clicks"

I've seen this is a common issue here on stack but it seems that the answer is always dependent on the specific scenario. I'm looking for a fellow coder to give me that "AHA" moment.
Problem: Ads posted to my website do not show the og:image content when shared to facebook until the ad is shared at least 4 times
I have thought about/ tried the following things
Checking the image size to make sure it's not large (128kb) is the norm. I compress all uploads.
Giving the ad some time to marinate before sharing (perhaps the fb crawler takes a while to cache the page)
I tried using the debug crawler tool on fb to see if I could reproduce the problem and I indeed could.
I tried sharing the ad to my own page regardless of the missing image to see if the image showed up on my wall. It did not.
The image will not show up on ANY shares until someone has clicked on the share icon on an ad at least 4 times. It seems to me like it might be some latency issue on facebook's part.
What could cause og:image to only show on subsequent share clicks?
Edit
Here's a test ad.
https://www.jdmxchange.com/Classifieds/Details/6ae72690-14d8-4bab-b039-3a2d79923794
Reading https://developers.facebook.com/docs/sharing/best-practices I found this, which might be just what you're looking for:
Use og:image:width and og:image:height Open Graph tags
Using these tags will specify the image to the crawler so that it can render it immediately without having to asynchronously.
This means, if you set the width and height of your og:image with tags, the image will show straight away.
UPDATE
Actually debugging your URL shows like this URL is redirecting to another page, and then another. Which makes me suspect the Facebook crawler is not able to access the actual OG meta tags you're using.
As a random test, I would add OG metatags to that last URL and see if Facebook uses them. But the actual solution would be to use URLs which are actually reachable to FB (no credentials necessary).

Sharing on Facebook returns no images, even if go:image is present and if linter says ok

here is my headache situation:
I have my weblog's single article page, if I try to share this page with the facebook like button, or with the old sharing bookmarklet, I get no image on Facebook post preview, and of course I don't get any image on my Facebook page too.
I can hear you say, well, check it with linter, sure, that's what I did, and this is what I've found so far:
Linter returns no error and it shows the right thumb image
if "after" the linter passage, I try to share the same page again, well, I get the thumb.
Do you have any idea of what's going on?
here you can see an example: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Flegrandj.eu%2Farticle%2Falain_baczynsky
this is the original page: http://legrandj.eu/article/alain_baczynsky
well, I know at this point it's not easy do debug, because I've "linted" almost all pages, but you can trust me, no images.
thank you!
if "after" the linter passage, I try to share the same page again, well, I get the thumb.
This is because you already tried to share them and they're now cached without images. If you want to get all pages fresh with image(s), you have to wait or re-lint every page you want to share in future. That's the only way to lift all caches immediately.

problem with facebook like button

I have placed the facebook like button on a website, and the weirdest thing is happening, every page on the site shows the same count for the number of people liking the site (~ 760), except the home page, the home page shows 18 people only.
for the life of me I cannot figure out what's causing this.
All pages are using the same open graph meta tags, and the facebook snippet is inserted by a user control (same on every page).
Anyone has any ideas where I can even start to debug?
The site is canvaspop.com
http://www.facebook.com/plugins/like.php?href=http://www.canvaspop.com/default.aspx&layout=button_count&show_faces=false&width=130&action=like&font=arial&colorscheme=light&height=21
Looking at the DOM and XHR Responses that data is coming directly from facebook without any problems.
to be perfectly honest, I would not rely too much on data coming from facebook, the amount load they have and there forever changing CDN, there's bound to be issues with the balance loader, that data as its the root of your domain may be coming from a cached result to decrease laod.
you can image the % of content delivered to homepage's rather then inner site pages, because users usually go on a site and then go off.
just wait it out and see if the results get updated. if it does not then go to the Developers Support areas and ask a member of the community or team!
Install fiddler, and look at the request sent to facebook on the homepage vs the other pages.