Twitter cards error--"ERROR: Fetching the page failed because other errors."


#1

Description of issue:

The twitter card validator is giving a vague error message:

ERROR: Fetching the page failed because other errors.

The other issue is that my picture isn’t showing up in the card.

URL affected (must be public):

Troubleshooting steps attempted [note that we will not prioritise posts unless there is evidence of following the troubleshooting guides]:

  1. Rewrote my robots.txt

It now reads:

# http://www.robotstxt.org
User-agent: *
Disallow:
  1. Switched my image url to an absolute path in my meta tags.
    The meta tags in my index.html are:

  <meta name="twitter:card" content="summary_large_image">
  <meta name="twitter:site" content="@naisnetwork">
  <meta name="twitter:title" content="Market View from NAIS">
  <meta name="twitter:description" content="Discover New Students With NAIS Market View">
  <meta name="twitter:image" content="https://www.nais.org/media/Nais/Homepage/Carousel%20images/Market_View_Slider_955.png">
  1. The card works for my staging site, although the image is still missing. My staging URL is https://market-view-staging.herokuapp.com/

  2. This leads me to think its something to do with the SSL on insights.nais.org, our production server.

  3. I ran the SSL Server test here: https://www.ssllabs.com/ssltest/analyze.html?d=insights.nais.org&latest. The results I got were all B’s. But I don’t know what that means.

Here’s the cert on prod, it’s SHA256.

Any ideas of what the problem is? Why is there an error loading the card on prod, and why can I not load the image anywhere?


#2

Hi Stephanie, I think you are right, it does look like an SSL issue here. Our crawler does some strict checking on certificate names and validations and unfortunately I’m not an expert, but it looks like there’s a problem validating the certificate chain. Interestingly it looks like the root of the domain (nais.org) is validating correctly.


#3

For anyone who has this same problem, here is what i did to fix it:

I uploaded the chained certificate to my server, instead of just the domain cert.

Thanks!


#4

thanks for sharing the resolution, glad to hear this is fixed for you!


closed #5