Problems Pulling Images on Pinterest and Twitter from Amazon CloudFront
I have a server that points to AWS ec2. - domain: -hometriangle.com
And the images are sourced from AWS CloudFront with SSL which internally points to ec2 .: domain: -static.hometriangle.com
Both Pinterest and Twitter are unable to fetch images. Whereas Facebook and Google do a good job of it.
Twitter Errors: I get the following logs in Card Validator
> INFO: Page fetched successfully INFO: 22 metatags were found INFO:
> twitter:card = gallery tag found ERROR: Internal Proxy Image Service
> Error (twitter:image0) ERROR: Internal Proxy Image Service Error
> (twitter:image1) ERROR: Internal Proxy Image Service Error
> (twitter:image2) ERROR: Internal Proxy Image Service Error
> (twitter:image3) ERROR: Internal Proxy Image Service Error
Pinterest errors: Oops Unable to complete selection / Something is wrong.
My robots.txt for cdn url looks like this
User-agent: Twitterbot
Disallow:
User-agent: Pinterest
Disallow:
User-agent: *
Allow: /robots.txt
Allow: /imagecache/*
Disallow: /
An example of used meta tags:
<meta property="og:image" content="https://static.hometriangle.com/imagecache/media/2916/htr-image-small-bathroom-390-2916.jpg?size=1200x630-3"/>
<meta property="twitter:image0" content="https://static.hometriangle.com/imagecache/media/2916/htr-image-small-bathroom-390-2916.jpg?size=1200x630-3"/>
If I replace the cloud URLs with direct URLs, the images are obtained. What could be the problem?
One of the Errorneous Page: https://hometriangle.com/photos/2/bathroom One of the Errorneous images: https://static.hometriangle.com/imagecache/media/2916/htr-image-small-bathroom-390-2916 .jpg? size = 1200x630-3
source to share
I also ran into this issue with Pinterest. Some experiments have shown that Pinterest has problems with Server Name Indication (SNI) -based SSL connections.
To demonstrate this, I created 2 new Cloudfront distributions. Both are SSL, one was using the default Cloudfront certificate and the other was using my own certificate and the required SNI. I don't have the budget to try the $ 600 / month SSL option, so I can't comment on this.
Both distributions were accessible through a browser using the Cloudfront URL over SSL.
Pinterest was able to pull the non-SNI out of the distribution, but was unable to connect to the SNI-based distribution.
I submitted a support request to Pinterest a week ago, but all I had was an automatic response. Bom-bom.
Here's a wiki on SNI. All major modern browsers support it, but I'm guessing what Pinterest wrote isn't working. http://en.wikipedia.org/wiki/Server_Name_Indication
source to share