ERROR: Fetching the page failed because other errors


#1

Whenever I share post via twitter share button from https://blogs.seqrite.com, unable to render card preview.

Please check below code to show twitter card for https://blogs.seqrite.com/everything-you-need-to-know-about-rbis-circular-on-basic-security-framework-for-primary-ucbs/

<meta name=“twitter:card” content=“summary_large_image”>
<meta name=“twitter:site” content=“https://blogs.seqrite.com”>
<meta name=“twitter:title” content=“Everything you need to know …”>
<meta name=“twitter:description” content="The recent spate of cyber-attacks … ">
<meta name=“twitter:image” content=“https://blogs.seqrite.com/wp-content/uploads/2018/11/RBI’s-Circular-on-Basic-Security-Framework-for-Primary-UCBs-300x169.png”>

Below is code to allow images for Twitterbot in robot.txt:
User-agent: Twitterbot
Disallow:

Kindly do the needful.
Our posts are not getting shared.


#2

Please update


#3

We are running into a similar issue that just started happening in the last two weeks.


#4

Your server does not support the appropriate SSL protocols (TLS 1.2), @anirudh235 . Per the troubleshooting post, the error you see in the validator is due to SSL issues.


#5

You haven’t provided a URL so it is impossible to troubleshoot @marxistvegan - but check the troubleshooting post first.


#6

Sorry about that, the url is https://solidarity-us.org
We went through the troubleshooting post, to no avail.


#7

Again, per the troubleshooting post, you’re seeing ERROR: Fetching the page failed because other errors. and this is an SSL configuration issue. Your site is not using a strong enough security cipher. We cannot do anything about this on our side.


#8

Andy I shared this with our tech person and they responded… Sorry to play the middle person…

As to a solution, you included this link in a previous message. I investigated and found that our certificate refers to “solidarity-us” while our server name is “solidarityus”. Twitter seems to object to the difference.

Is this the issue?


#9

It could be. I ran the site through the ssllabs.com test and it showed a low result. We cannot help there.


#10

Thanks Andy


#11

Thanks, we have updated and our ssllabs has improved to a B if you can recheck and advise on what configuration changes we could make we would appreciate it.


#12

Looks like that’s validating OK.