Hi Onema,

I'm unfortunately not familiar with this family of PHP libraries and how
they handle opening HTTP connections using that custom non-standard URI
scheme ("ssl://") -- it might be handling the correct protocol for you
behind the scenes. Error #0 is not an error sent by the Twitter API so it's
likely being sent/interrupted locally within your own machine or a load
balancer or proxy between your server and Twitter API -- likely it would
seem because the protocol is incorrect.

Was there some kind of documentation you were working from when implementing
using these new libraries?

Taylor Singletary
Developer Advocate, Twitter

On Mon, May 24, 2010 at 10:31 AM, Onema <kinoj...@gmail.com> wrote:

> Hello, 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
> Onema
> 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.

Reply via email to