Thanks for the suggestions. It turned out that my hosting provider
had blocked port 443 so outgoing https communications weren't working.
I was able to test this once i got shell access and could try a
command-line curl and then when that didn't work try to telnet to port
443 on a random https site. That not responding led me to realise
port 443 was being blocked.
Happily they just unblocked the port for me so all is now good.

cheers,

- Rory

On 1/9/06, Kevin Carothers <kevindotcar_at_gmail.com> wrote:
>
> I don't know if it's related, but I got a similar error from the
> command-line (curl.exe) when the cacert.pem file was not readable.
>
> KC
>
>
>
> On 1/8/06, Daniel Stenberg <daniel_at_haxx.se> wrote:
> > On Mon, 9 Jan 2006, Rory wrote:
> >
> > > However, I always receive either a CURLE_OPERATION_TIMEOUTED (28) or
> > > CURLE_COULDNT_CONNECT (7) error.
> >
> > When you do what? Do you use a proxy? You tried without setting the timout
> to
> > 10 seconds?
> >
> > > CURL Information libcurl/7.12.0 OpenSSL/0.9.6b zlib/1.1.4
> >
> > This libcurl version is considered very old (June 2004), and vulnerable to
> > several security flaws. And so are in fact both the OpenSSL and zlib
> versions
> > too!
> >
> > > Do I need to do anything special for https?
> >
> > Yes, sometimes. But those error codes would not be the ones you get that
> would
> > signal that you need to do something.
> >
> > --
> > Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
> > _______________________________________________
> > http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
> >
>
>
> _______________________________________________
> http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
>
>
>

_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
Received on 2006-01-11