CODEWITHSUNDEEP
laravelsslnginxtwitter
LearningPath
LearningPath

Reputation: 661

Twitter: "Fetching the page failed because other errors", on Forge NGINX server with SSL

Our website is running on Laravel Forge with 'Let's encrypt SSL,' and HTTPS is OK in the browser. We added FB, Twitter meta tags for having branded FB and Twitter cards when sharing on these media.

Following 'ERROR: Fetching the page failed because of other errors. ' is raised when trying to display Twitter card in tweets (tested with https://cards-dev.twitter.com/validator) and this is linked, after research, to this dedicated well-known issue:

https://twittercommunity.com/t/error-fetching-the-page-failed-because-ssl-handshake-error/30204/9.

It establishes that on Apache server serving different sites, a ServerName directive that matches the SSL certificate’s CN is needed to avoid Apache sending the local hostname or the IP of the connection.

How to solve this Twitter issue on Forge NGINX server? Does someone know if this is the similar issue as Apache server and what configuration changes are needed?

Upvotes: 4

Views: 4941

Answers (1)

George Haskell
George Haskell

Reputation: 131

I've lost the better half of a day on this issue, likely digging through the same threads as you. This thread held the answer: https://twittercommunity.com/t/twitter-card-error-fetching-the-page-failed-because-other-errors/112895/6

Enabling AES128 as an ssl cipher will allow the Twitterbot to connect. This can be done within the nginx configuration within the Forge UI.

Happy tweeting!

Upvotes: 7

Related Questions