Warning: ******* is unreachable

Can you paste the complete and exact warning message?

This most likely means that Facebook is unable to connect to your site. Do you have a firewall set up that could block this connection?

There error that Facebook returns is very clear:

http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww....

Response Code: 200
Fetched URL: http://www.salechile.cl/contenido/datos/comida-peruana-en-el-centro-de-s...

Could Not Follow Redirect Path: Using data from http://www.salechile.cl/contenido/datos/comida-peruana-en-el-centro-de-s... because there was an error following the redirect path.

Bad Response Code: URL returned a bad HTTP response code.

However, when I look at the page now, the error doesn't seem to be there anymore. Is this correct?

It might be a temporary issue with Facebook, since the error vanishes once you go to the developer's page. It could also be an issue with the server you're hosting the site on with the way it handles path aliases for example.

i'm experiencing something similar - how were you able to make the error go away after visiting the fb dev page? I've got the comments working on some pages, but not all, it's quite strange.

Same problem here... after refreshing page a couple of times, it disappears...

Note: my site is still in development, so in maintenance mode... but even when I take it online, the error keeps showing up. Does Facebook need some time to get the url?

I got the same problem, but In my case it appeares only on stranslated pages, that automatically get the language code after the domain name, like http://mydomain/nl/blogpost1 in which nl is the translated, dutch version.
In the error message, facebook is trying to connect with the URL that does *not* contain the language code, 'nl' in my case.

So as far as I can see, this module currently is not compatible with the drupal multilanguage modules.

Setting issue to active since I am able to reproduce it with the multilingual modules. I'm just unable to identify what's causing it, so please give me a hand,
Thanks

I really would like this plugin to work with multilingual drupal sites. Any chance that someone takes a look here?

I think that the problem lies inside facebook_comments.module file at this line:
$url = $base_url .'/'. drupal_get_path_alias($_GET['q']);

That code rips off the language part, to get the full path you have to change that line to:
$url = $base_url . drupal_get_path_alias(request_uri());

I think that you will still get the error if you are trying it in localhost with your site being inaccessible from the internet, but this shouldnt be a problem.

I'd like to know if this works for you folks.

Thank you,

Geeo

I couldn't find the issue number anywhere so the filename should be improved.

File reposted with correct name convention

@Geeo: #16 works fine! Thank you very much! Let's see if something shows up after using it for a while, but the error is gone now.

Nice work all, thanks! I will commit this soon.

This has been committed: https://drupal.org/commitlog/commit/30180/5ce57607adab692fe25c610ff0b423...

Thanks all!

But this fix only addresses the language compatibility, right?

The original issue still exists being that some URL's don't seem to work with Facebook for no apparent reason.

If you can give instructions to reproduce the bug the community can give it a try, otherwise it is fairly impossibile for anyone to fix it.

I think this bug is not related to Facebook social plugings...I receive the same message in Fb comment: Warning: ******* is unreachable.
but i also have problem to embed these specific content types into Facebook timeline. even if i turn this module off...
In specific i get this warning with core blog module...

trying patch and Here is what I get:

This was the output from patch:

Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/facebook_comments.module b/facebook_comments.module
|index 68a1cc8..ab967ad 100644
|--- a/facebook_comments.module
|+++ b/facebook_comments.module
--------------------------
Patching file facebook_comments.module using Plan A...
Hunk #1 FAILED at 350.
1 out of 1 hunk FAILED -- saving rejects to file facebook_comments.module.rej
done

Any Help?

I had the same problem and solved it by activating the module "Open Graph meta tags" that comes with the module "Metatag" (http://drupal.org/projects/metatag).

Not explain well because it was solved, but there it is.

Please someone check if this module solves the problem.

(Excuse the Google translation)

I am having the same issue and I am not using a multi-language site. I am using some url re-writes using url aliases.

By the way, I presume the poster above is referring to this module:
http://drupal.org/project/metatag

I have downloaded and enabled it and the included Meta tags: Open Graph module. I will report back if this has any effect.

It has been a couple days. I am reporting back that diegodf's fix in #24 above still seems to be working. I have NO idea why, but I also have no yellow "Warning" about unreachable nodes.

Thanks for sharing that fix.

I ran into this issue on a Drupal site installed in a subdirectory (e.g. www.example.com/drupal). In my case, the subdirectory path was being repeated in the Facebook Comments Box URL (e.g. www.example.com/drupal/drupal/...).

This appears to be a regression from the patch in #16. Specifically, the module was concatenating $base_url with request_uri(), both of which include the subdirectory path, resulting in an incorrect URL. I have attached a patch that uses a more robust approach for generating an absolute URL for the current page. This solves the "*** is unreachable" issue for me. Can someone verify that the patch works for multilingual sites, as described in #11?

Note that I am not using the metatag module. From what I can tell, it appears that this "unreachable" message is caused by incorrect data attributes on the Comments Box iframe, rather than the meta tags elsewhere in the page.

Finally, I'm changing this to a major issue, as using the wrong URL for the Facebook Comments Box plugin will cause any submitted comments to be associated with the wrong object in Facebook's Open Graph.

i confirm patch #27 solve my problem. totally my site also was installed in subdirectory. applied this patch, no more error from FB.

double confirm :) #27++

+1 to this being major. It's an even bigger deal because if you comment on

http://www.website.com/blog/post/1

It gets shared on Facebook as

http://www.website.com/blog/post/1?fb_action_ids=10103359098142200&fb_ac...

SO when friends and coworkers click on that shared comment on Facebook, they don't see any comments (even though their path was the result of one).

The patch in #27 is essential to fixing this problem, as it makes both links above jive for showing related comments.

Thanks for the patch!

Committed, thanks!