I'm getting a critical error when using the Facebook Linter to check og meta info.
Critical Errors That Must Be Fixed
Error Scraping Page: Can't Download
https://developers.facebook.com/tools/debug/og/object?q=theshinebox.com
The site/url work fine in a browser though...
I haven't checked this, but it looks to me like your og:url value is incorrect.
Facebook will actually GO to that address to get the canonical version of the page. And you've written the address without the Top Level Domain, so of course Facebook can't download from it.
David
Related
I have an e-commerce website and I want to share a link on my Facebook profile.
When I do I get a 404 - File or Directory not found even though the URL is working properly when you click on it. Below is what I see exactly:
I have tried:
To post the URL with https:// or without
https://developers.facebook.com/tools/debug/og/object
https://developers.facebook.com/tools/debug/sharing/
None of these solutions work!
The Sharing debugger shows this error:
But I don't understand how the error is legit since I have the parameters it's asking on my Page's Header tags.
What exactly is wrong?
I had the same problem at some point and the issue was that the team who manages our server had blocked the bots of Facebook and other search engines from entering our website and they forgot to undo this! Have a look if this is the reason in your occasion.
I tried to create a post (using a blogger URL) in the Facebook Power Editor.
Result:
Error creating posts. Please retry later. You can also go to your Page and post from there. (OAuthException) (#1500) The url you supplied is invalid
Then tried to install Facebook's Open Graph tags into Blogger to see of that would fix the problem.
To test the OG tags I used Open Graph Object Debugger.
Here are the results:
Critical Errors That Must Be Fixed, Error Linting URL, An internal error occurred while linting the URL.
How do I fix the invalid URL and the Critical: Error Linting URL?
I am not tech savy so this issue is way over my head but I would like to get it fixed. Please help.
Thanks
I had a problem like this with the og:image pointing to an image hosted on Rackspace. The URL was something crazy like
http://1234567890abcdef1234-1234567890abcdef123456780123412b.r23.cf5.rackcdn.com
I think the Facebook linter was seeing this as spam, because if I actually embedded the image in my app/assets it worked fine, so it wasn't the image that was the problem.
The solution was to set up a CNAME on my hosting provider that pointed to the hideously long Rackspace URL, e.g.
CNAME Value
images http://1234567890abcdef1234-1234567890abcdef123456780123412b.r23.cf5.rackcdn.com
Then I changed the og:image meta tag to be
meta property="og:image" content="http://images.mydomain.com/relative_rackspace_imagepath.jpg"
I wanted to contribute a little data point here as this is currently the top google result for this error and there is little useful info out there.
In my case, the page was a post on a wordpress blog that happened to begin with a twitter post embed, and the twitter post happened to contain an url. My og tag plugin grabbed the embed and managed to place the url along with a little other cruft in og:description, and once I cleaned that up manually the error disappeared.
I think the lesson is that when this happens take a look at your og tags for the page for ANYTHING unusual. That's the place to start.
Happened to me once my og:image pointed to this url:
http://xxxxxxx.appspot.com.storage.googleapis.com/IsraelFlag.jpg
I just changed it to:
http://storage.googleapis.com/xxxxxxx.appspot.com/IsraelFlag.jpg
and it works
probably very poor software parses the html
I spent hours trying to debug why this was happening for our site. It turns out it was because of the og:locale:alternate meta tags we had.
<meta property="og:locale:alternate" content="cs_CZ" />
<meta property="og:locale:alternate" content="de_DE" />
...
When Facebook sees this in your tags they subsequently hit your og:url with '?fb_locale=[lang]' where [lang] is each of your alternates. There is one request per alternate. In our case, we had code that was returning back a 302 on that request. As a result, the Facebook Open Graph Object Debugger kept saying "Error parsing input URL"
Once I fixed the responses to the alternate requests to actually return internationalized content, the issue was fixed.
The facebook debugger is giving 500 error for your webpage. It is unable to get my og metatags values. However, og metatags are present in the web page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fstaging.eco.ca%2Fcommunity%2Fblog%2F5-fascinating-green-jobs-youve-never-heard-of%2F68170%2F
Take a look at your IIS configuration. Something in there is refusing connections from anything that isn't a web browser.
Your page returns a 500 error for the W3C validator also.
For me it was because when Facebook, Google or other robots access the page, they don't send a language like a browser does, and in the code we were using the browser language to determine the content language.
I want to share my experience about this facebook debugger 500 error. I was getting this error without any explanation on facebook debugger. I checked my server side and domain records, tried what I found on internet with no luck. It took me long time to discover the problem.
Problem was I was sharing url within a restricted area in my website while sharing for first time. Let me explain, I have a test page in my cms, before I publish anything, I test if everything's ok. I realised whenever I test a content, facebook tries to crawl site, but it's in a restricted area. So I moved anything about facebook from my test page.
I'm just trying to use standard link sharing using Facebook's sharer.php url. Here is a sample link:
https://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Fbsfurl.com%2FhTM9%2F2%2F2&t=Welcome!
I've been doing this successfully since 2009. Recently the Facebook sharer page seems to no longer be able to access my link to pull in images and a description. Using the Facebook Object debugger,
https://developers.facebook.com/tools/debug/og/
I see that every URL that i try returns a HTTP 502 error. Can someone help me understand why this is happening? Even a static HTML page returns this same error. Here is a screenshot of the error: http://images.publicaster.com/ImageLibrary/account116/images/facebookscrapeerror.png
Testing the URL in a browser works fine: http://stagingclick.publicaster.com/test.htm. this is just a static link no dynamic content, no redirects nothing. I'm a little at a loss of what i can do to fix this error. In my IIS logs i am not able to see the incoming request from Facebook's scraper.
Thanks!
-mark
The page you linked (http://stagingclick.publicaster.com/test.htm) is redirected (via the og:url tag) to http://www.nin.ja which doesn't resolve - are you sure there isn't a similar problem with the live links you're sharing?
Having some issues with the feed dialog when attempting to post to a event or fan page. In my application I am using the JS API and FB.ui using the method feed.
But for a demonstration you can do it using the feed url too for example:
http://www.facebook.com/dialog/feed?app_id=131727613511269&to=287203454659917&redirect_uri=http://www.timeanddate.com/
After clicking share you get the:
Sorry, something went wrong.
We're working on getting this fixed as soon as we can.
Where:
app_id = your app
to = a event / fan page
redirect_uri = a url you are allowed to redirect to
note that the app has publish_stream permissions. (it also has manage_pages for fan pages)
The app in question by the way is: http://apps.facebook.com/tndcountdown/
Thanks,
Andy
EDIT:
An Example taken straight from the documentation:
http://www.facebook.com/dialog/feed?app_id=123050457758183&link=http://developers.facebook.com/docs/reference/dialogs/&picture=http://fbrell.com/f8.jpg&name=Facebook%20Dialogs&caption=Reference%20Documentation&description=Using%20Dialogs%20to%20interact%20with%20users.&message=Facebook%20Dialogs%20are%20so%20easy!&redirect_uri=http://www.example.com/response&to=287203454659917
just replace to=287203454659917 with an event.. (make a test one like it did there)
A few issues I've run into will dialog is that Facebook tries to fill in any missing data. So if you don't provide a description and caption, Facebook will try to scrape the page to get that content. Depending on how the page responds to the "scraping" Facebook will error out. I always make sure I include at least a space for those fields.
It seems the feed url you provided is similar to what is in the documentation. But the demo in the documentation has extra parameters.
I'm about to add page support to my Facebook app, which does the same thing as yours.
http://apps.facebook.com/countdown-timer/
As I posted here - Facebook Send Button - 'Sorry, something went wrong.'...
I had the same problem & worked out that this was due to linking to a Facebook page that did not have a vanity URL set up (i.e. http://www.facebook.com/CubicMushroom rather than http://www.facebook.com/profile.php?id=261963707177053). If you set up a vanity URL for the page it seems to work OK (providing you link to the vanity URL version of the page URL).
To claim a vanity URL, once you have a certain no of like (it used to be 25, but think it's a little lower now) visit https://www.facebook.com/username/