Could not open socket - Errno 13 - Errstr "Permission Denied"

[fsockopen error dude]

I'm using the following code

if( false == ( $fs = @fsockopen($host, $port, $errno, $errstr,
10) ) ) {
die ('Could not open socket in fsockopen - ' . $host .
":" . $port . ":" . $errno . ":" . $errstr);
}

and I get the following result;

Could not open socket in fsockopen - api-verify.recaptcha.net:
80:13:Permission denied

My hosting plan is through Aplus and they have granted me outbound
access on api-verify.recaptcha.net:80.

Can someone tell me why I might be getting this error or how to fix it?

[Jorge Peña]

This might be what you're referring to: http://code.google.com/p/recaptcha/issues/detail?id=26

--
- Blaenk Denum

[fsockopen error dude]

Thanks for the link. But it still gives the same error.

On Nov 19, 7:45 pm, "Jorge Peña" <jorgepbl...@gmail.com> wrote:
> This *might* be what you're referring to:http://code.google.com/p/recaptcha/issues/detail?id=26

[fsockopen error dude]

Does anyone know if who/what is denying the "permission" in this case?
Is it the Captcha server denying permission or my server denying
permission to open a socket?

On Nov 20, 11:48 pm, fsockopen error dude <yojiffyski...@gmail.com>

wrote:
> Thanks for the link. But it still gives the same error.
>
> On Nov 19, 7:45 pm, "Jorge Peña" <jorgepbl...@gmail.com> wrote:
>
> > This *might* be what you're referring to:http://code.google.com/p/recaptcha/issues/detail?id=26
>
> > On Wed, Nov 19, 2008 at 1:09 PM, fsockopen error dude <
>
> > yojiffyski...@gmail.com> wrote:
>
> > > I'm using the following code
>
> > >       if( false == ( $fs = @fsockopen($host, $port, $errno, $errstr,
> > > 10) ) ) {

> > >                die ('Could not opensocketin fsockopen - ' . $host .

> > > ":" . $port . ":" . $errno . ":" . $errstr);
> > >        }
>
> > > and I get the following result;
>

> > >       Could not opensocketin fsockopen - api-verify.recaptcha.net:

[derek]

We've been having the same issue with our host, aplus.net. Their
firewall is IP based, so we added 64.34.251.152 and 69.12.97.166, but
we're still getting the fsockopen failure. We're using the stock
recpatcha code, so we know that's not the issue. But at this point,
they are insistent it's the code. We out of options, so it looks like
we're going to move to another host.

[reCAPTCHA Support]

SELinux may be causing this issue.

- Ben

--
reCAPTCHA: stop spam, read books
http://recaptcha.net