Question

I am moving from the basic authentication method using username
and password to the OAuth based authentication.

I was using an old version of the pear package Services_Twitter, that
did not support OAuth.
The latest version of this package supports OAuth authentications, it
has a few dependencies (HTTP_Request2, HTTP_OAuth).

It was very simple to install them and upgrade the package. I did all
this my local machine and had no trouble getting the authentication up
and running.

I committed this code to the test site, but every time the code
request a “request token” I get the following error message “Unable to
connect to ssl://api.twitter.com:443. Error #0″

I have spend 6 hours making sure that all the pear packages where up
to date, checking the customer token and token secret, making sure
port 443 is not closed… in addition to various other test.

I have exhausted my resources and I come to you in hope to find some
answers.

Thank you

PD: One of the things I do not understand is why does the message says
that the url is ssl://api.twitter.com:443 rather than
https://api.twitter.com/request_token? the former one is the one I am
using to get the request token.

Answer 1

“Unable to connect to ssl://_______:443. Error #0” generally means that there is a ssl_verify_peer or certificate match issue – and the twitter API doesn’t require you to provide a certificate!

HTTP_Request2 sets the ssl_verify_peer option to true by default – which is fine if you are specifying a certificate for establishing a connection so perhaps you need to check that setting is switched off?

This is checked for you in Services_Twitter if the use_ssl config setting is enabled so at a guess you may need to check that is set?

e.g.:

$twitter = Services_Twitter_factory('statuses/update', true, array('use_ssl' => true));