I’m using a PHP class of abraham/twitterOAuth and I noticed that Twitter api.twitter.com now requires SSL/TLS.
It is very inconceivable. One of my API works fine. I have not opdate anything yet.My two API are used with different severs .Now I am wondering it is sever problem or twitter SSL issue .
Run curl --verbose “https://api.twitter.com/1/help/test.json”
[root@pppppp]# curl -3 -capath --ssl https://api.twitter.com
-bash: file: No such file or directory
[root@ppppppp ~]# curl --verbose “https://api.twitter.com/1/help/test.json”
- About to connect() to api.twitter.com port 443 (#0)
- Trying 199.16.156.104… connected
- Connected to api.twitter.com (199.16.156.104) port 443 (#0)
- Initializing NSS with certpath: sql:/etc/pki/nssdb
- CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
- NSS error -5990
- Closing connection #0
- SSL connect error
curl: (35) SSL connect error
[root@ppppppp ~]# traceroute api.twitter.com
traceroute to api.twitter.com (199.16.156.104), 30 hops max, 60 byte packets
1 erver.ch1.hos.net (197.872.2.98) 0.029 ms 0.017 ms 0.015 ms
2 0-63.gw1.chi.hos.net (65.85.46.885) 0.394 ms 0.375 ms 0.448 ms
3 eqix-ch2.twitter.com (206.223.119.171) 0.462 ms 0.447 ms 0.410 ms
4 199.16.159.34 (199.16.159.34) 28.539 ms 28.494 ms 28.581 ms
5 ae50.atl1-er1.twttr.com (199.16.159.73) 47.281 ms 44.621 ms 44.565 ms
6 199.16.156.104 (199.16.156.104) 43.593 ms 46.474 ms 46.426 ms
Can anyone tell me what problem my API have? How should I fix it?