#1

Description of issue:

The Twitter Card Validator gives the answer: “ERROR: Failed to fetch page due to: HttpConnectionTimeout.”

URL affected (must be public):

We have 2 site mirrors (the same page content, robots.txt, ssl, no firewalls, etc.):

  • https://test1.coroot.com - HttpConnectionTimeout in 19 out of 20 tries
  • https://test2.coroot.com - validates perfectly

We have read the troubleshooting guide and other threads on this issue several times.

Please help.

#2

Any help from twitter staff, please.
On who can do ping and curl from “Twitter’s aggregate outbound IP ranges are 199.16.156.0/22, 199.59.148.0/22 and 192.133.76.0/22”.
Our provider (OVH) says it doesn’t block anything.

#3

I’m not clear on why this is happening (except that test2 resolves to a different IP than test1 or the based of the domain). In the case of both test1 and coroot.com base, they seem to only connect on a rare occasion from the crawler / validator, but test2 is working. I don’t have any more detail information than that - a timeout on 147.135.104.11 but 138.201.250.40 goes through OK. I guess it could be some kind of routing thing but I’m unable to trace that.

#4

andypiper, thank you for the try!
Is there any way to ask someone on the Twitter network operations team for more details about this?

#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.