Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Critical Error Linting URL: An internal error occurred while linting the URL

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

like image 721
user2807656 Avatar asked Nov 23 '13 23:11

user2807656


2 Answers

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"

like image 86
mdenomy Avatar answered Oct 30 '22 15:10

mdenomy


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.

like image 39
Mark Seifert Avatar answered Oct 30 '22 16:10

Mark Seifert