thread on Stack Overflow covering the same problem dates back to 2012, but with entries as recent as four months ago.

The fix: Implementing an HTTP link instead. According to the thread, users resolved the issue by using an HTTP URL instead of HTTPS. One entry on Stack Overflow claimed Facebook was aware of the problem and, at the time, was looking into it. “I ran into the same problem and reported it as a bug on the Facebook developer site. It seems pretty clear that og:image URIs using HTTP work just fine and URLs using HTTPS do not. They [Facebook] have now acknowledged that they are looking into this,” wrote Keegan Quinn in January 2012.

Why we should care. For brands already struggling to gain traction with organic content on Facebook, a glitch that removes or replaces images from posts is one more obstacle. With the Facebook debugger claiming the error is a corrupted file, marketers may not realize that the problem might not be the image, but perhaps Facebook’s issue with HTTPS links.

We’ve asked Facebook for a comment and will update this story if we get a response.

About The Author