Can not identify issue with SSL implementation


Description of issue:

I have not been able to identify the issue with my web site’s SSL implementation, which is preventing Twitter from rendering cards for my web pages.

I have read the “Not Whitelisted, unable to render, or no image: READ THIS FIRST” article, and referred my web site host’s technical support to it. However, they have been unable to identify the issue with the SSL implementation at my web site. The line in the article “if you see a validator message about Fetching the page failed because other errors or similar…” seems to describe my situation perfectly, but my provider tells me that this does not apply in my case, because they are not using an Apache server.

Twitter is unable to render cards when I use https URLs for my web pages, or when those web pages’ meta tags contain https links to the card images. However, if I use an http URL to my web pages and the meta tags similarly use http links to the card images, it works perfectly.

I realise that this likely means that my web site’s host has improperly implemented the SSL certificate at my site. I should be grateful for any advice on what their precise error is, and how they could correct it.

Thank you in advance for your assistance.

URL affected (must be public):

Example of a problem page, using an https URL and https meta tags -

Example of a functioning page, where both the URL and the page’s meta tags all use http -


It is definitely an SSL issue, but it is not the same as the SNI issue described for Apache.

$ curl -A Twitterbot
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to

I’ve never seen that error before, but I would have expected curl to be able to fetch the page, and the fact that it exits with an SSL exception points to some kind of configuration issue on the server side. It looks like there are a variety of insecurities you might want to look into.


Thanks @andypiper for conveying the error message to me. I have sent the information to my web site host, in the hope that they will be able to employ it to identify their SSL configuration error.


This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.