Check out this result of debugging an article using Facebook debugger.
It comes up with this warning:
og:image should be larger. Provided og:
Another issue that could cause this is the use of characters like # in the filename.
Allthough browser will show them correctly, facebook will give an error stateting the img is to small, while infact it isn't able to read it.
So make sure you image filename only uses the standard characters A to z, _, -, 0-9
If someone is still running into this issue, even though facebook's scrapper correctly scrapes the image of size >= 200x200, wait an hour and go have coffee. Come back and hit debug again and it should be fine. It takes time for facebook to update its stored graph data.
Try to add this:
<meta property="og:image:width" content="200" />
<meta property="og:image:height" content="200" />
If the image url is https:// and Facebook has problems reading your SSL certificate, it will produce this rather unhelpful error message. To test, see if a http:// url for the image works. If it does, your CA certificate may need some tweaking. Try Googling "Curl Error : SSL_CACERT SSL certificate problem: unable to get local issuer certificate"
Note: Even if your page has no problem displaying with a https protocol, Facebook digs deeper to confirm your identity. I think this is relatively recent. Considering their whole fake news debacle I'm not going to be too upset.
I had
<meta property="og:type" content="website" />
in the meta tags.
Removed that line and it worked, so current tags look like this:
<meta property="og:title" content="PUT TITLE HERE" />
<meta property="og:url" content="http://www.example.com" />
<meta property="og:image" content="http://www.example.com/images/myimage.jpg"/>
Define og:image:width and og:image:height parameters like @Maria has suggested.