Somehow sharing a link to a website that has a Let's Encrypt certificate doesn't work with Linkedin. Via an unsecured connection the open graph tags and images are fetched correctly, but via SSL these remain blank.
Any help would be appreciated.
I would start with some general troubleshooting of your SSL configuration, let SSL Labs run against your site and fix any issues (e.g. missing intermediate certificate, etc.).
If that doesn’t help with your problem, it probably means LinkedIn is using a trust store without the cross-sign root CA Let’s Encrypt is using. This might be the case e.g. if they use Java with Oracle’s default root store. I would imagine if this gets reported a lot, they’ll eventually add the CA to their store.
It’s a Linkedin trust issue as I’ve been having the same problems on multiple sites, all of which have passed the SSL Labs test with flying colours.
I’ve tried reporting it to Linkedin support, but they don’t seem to understand the issue!
As long as you don’t force your connections to redirect to https, Linkedin will retrieve the information via http. But that’s not really the point 
Although this is an old thread it is still an issue. It is a LinkedIn trust issue and for me that was a reason to switch to a paid SSL certificate just for the sites I want to share from.
I also contacted LinkedIn support and they really don’t understand. Anyone who got Let’s Encrypt SSL trusted by LinkedIn let me know 
1 Like
And four more years after, we still have the same issue. My zaps fail because LinkedIn doesn’t trust the R11 intermediate certificate.
SSLabs complains on CRL availability for R11.
Noone should trust intermediate certs, including LinkedIn.
That's fine.
3 Likes