SslHandshakeError on Card Validator

[dssupport]

Nope, we fixed it, thanks!

[iainbeeston]

Hey @jbulava, we’re having the same issue for https://www.new-bamboo.co.uk - could you please take a look at that? I’d really like to find out what the underlying problem is

[jbulava]

I will reach out to the engineering team about the SSL error as I am unsure myself. Apologies for the trouble.

[haobcheng]

Hey @jbulava, is there any update on this? We’re running into the same issue with CloudFront and moving to an implementation that does not require any SNI would be a major hurdle for us. Other popular crawlers and bots work fine. Fixing this would require us to eliminate the benefits of our CDN and SSL offloading.

[sshreyas]

Hey,

Any update on this? Anyone using Cloudfront and Amazon right now cant use Twitter cards.

–
Shreyas

[apassant]

Hi @jbulava, all

I have a similar issue with my domain - can’t validate the card as it complains about the handshake error. Yet, my website lods w/ SSL correctly on the browser, e.g.

https://www.yapme.co/y/ag1zfnlhcG1lLWRvdGNvchILEgVNZWRpYRiAgICA1LqGCQw

I’m using SNI for my certificate and found that it fails on command line with

openssl s_client -connect www[DOT]yapme.co:443

but works with

openssl s_client -servername www[DOT]yapme.co -connect www[DOT]yapme.co:443

(Had to use [DOT] to make the post valid in the previous commands)

So I’m wondering if you support SNI w/ SSL?

Thanks!

[JonathanGirven]

We are having the same issue with Google App Engine.

[jspraed]

+1 We are seeing the same problem.

[iainbeeston]

@jbulava Any update on this? We have no problems with Facebook or Google Plus, but Twitter cards integration seems pretty broken right now.

[leozc]

https://www.new-bamboo.co.uk

We have deployed a new release, would you please try again?
https://cards-dev.twitter.com/portal/validation

[NightSurge]

I too am getting this error. I just noticed that none of the links were showing the cards lately, and I did just add SSL to my server a few days ago. What gives? As others have said, Googe, Twitter, etc works fine. It is only twitter cards that are currently giving errors for my site after adding SSL.

[joncipriano]

Just checking in to see if this is still an issue for people. All URLs provided above (that also have Twitter meta data) appear to be validating correctly.

@NightSurge, you are the last person to post after a fix was implemented. If you are still having an issue, please reply with a URL to debug.

[NightSurge]

https://xboxdvr.com/DiPN%20D%20Dizzy/3f96633e-e368-4d57-aeb3-e5c95f56324f

Still getting error. If I simply remove the s from https it works, but my site uses SSL, so I can’t simply do that.

[iainbeeston]

Our site now works, but we’ve moved to a different infrastructure.

[QuoteFlare]

our site quoteflare.com is still getting this same error
twitter cards are getting a 404 error where the image is supposed to be when you open them.

[CarltonJefferis]

@joncipriano We still have the same issue. Using Amazon infrastructure with a wildcard SSL for our domain. This URL fails when we try to validate using the Card Validator:

https://thedigiterati.com/test-post/

Please help!

[yhenry]

@CarltonJefferis, I’m unable to reproduce the SSL error with your url, can you check again pleased? Thanks.

[CarltonJefferis]

Apologies, it wasn’t an error on your side in the end. Instead, this was the issue: http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0
All fixed and working now. Thanks for your support.

[tibor]

I have the same problem with all of my domains hosted by uberspace.de, the certificates are working fine though in all browsers, for google and facebook:

tibormartini.de
tibor.link
wikiwissen.org

The Card Validator responds to all of them with „ERROR: Fetching the page failed because SSL handshake error.“.
Uberspace is using 4096 bit encryption, so the theory is that this causes problems with Twitter Cards since Twitter supports only 1024 bit encryption afaik?

@jbulava, could you take a look?

Thanks,

Tibor

[kafeelahmad1]

Hi,

I am getting the same error. My url is enter link description here