Thanks Ralph. Glad you got yours working. I will try this on our site.
Im having the same problem, and the log only show minimal info “ERROR: Fetching the page failed because other errors.”. I tried @ralphsnart .htaccess solution, but no success. The Url: https://riskinnovation.asu.edu/ @andypiper can you take a look at the log and give me some more info?
Make sure you’re not blocking Twitterbot. Add this to the end of robot.txt…
Also, your validating url and image meta url needs to be http and not https.
handshake alert: unrecognized_name at remote address which almost certainly means your web server’s SSL settings are not correct. There are a few threads like this one and this one which refer to ways to resolve SSL issues so that strictly-configured Java-based code can work with them.
thanks @andypiper that helped, I reconfigured my settings and resolved the issue.
SSL was not helpful for me, please check my application heropay.com based on django-python framework.
andypiper please help in this.
I also get
handshake alert: unrecognized_name at remote address from an SSL connection to your site, so I believe this is likely to be a similar issue. Your certificate has a wildcard name of
subject=/CN=*.heropay.com which is not an exact domain match, per the other threads I linked above, try modifying your
Also, please don’t tag individual members of Twitter Staff for help, since we may be unavailable from time to time.
Unable to render Card preview
andypiper Can you help to check my domain also : https://www.giantsingapore.com.sg/about-us/our-retail-formats/
I recive the same error message,.
Same issue, so I suggest you check the other threads I linked above for ideas to help to resolve the problem with your site or server’s SSL setup.
@andypiper I’ve got the same issue with our web app. Currently there the SSL/HTTPS is disabled. When I copy the input of our crawler-page onto another webserver and serve it as a static file, it works fine.
When I run the card validator there’s no request logged.
The page is running on port 8080. Maybe that’s a reason, don’t know.
The server is listening for a user agent matching
/twitterbot/gi and serve the related static crawler-page.
If you’re able to run it without an explicit port I suspect that may help.