ssl_error_rx_record_too_long

[airdrummer]

i followed the ssl faq (http://mdp.cti.depaul.edu/AlterEgo/default/
show/140) then tried to access https://127.0.0.1:8888/admin:

Secure Connection Failed

An error occurred during a connection to 127.0.0.1:8888.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)

The page you are trying to view can not be shown because the
authenticity of the received data could not be verified.

can i buy a clue, please?-)

[Daniel Contag]

Could it be that your browser rejects the certificate because it is self-signed?

Just a guess.

Daniel

[Mark]

Hi airdrummer

I have been experiencing the same issue and was confused by that
AlterEgo entry. According the Mozilla SSL error code page here (http://
www.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html)

"This generally indicates that the remote peer system has a flawed
implementation of SSL, and is violating the SSL specification."

What happens if you try getting web2py to bind to port 443 instead of
8888.

Perhaps someone else can explain this?

On Nov 4, 2:39 pm, airdrummer <airdrum...@wheel.org> wrote:
> i followed the ssl faq (http://mdp.cti.depaul.edu/AlterEgo/default/

> show/140) then tried to accesshttps://127.0.0.1:8888/admin:

[mdipierro]

I do not know but this is a ssl error. Is the error generated by the
server or the client?

Massimo

On Nov 4, 9:08 am, "Daniel Contag" <con...@gmail.com> wrote:
> Could it be that your browser rejects the certificate because it is self-signed?
>
> Just a guess.
>
> Daniel
>

> On Tue, Nov 4, 2008 at 15:39, airdrummer <airdrum...@wheel.org> wrote:
>
> > i followed the ssl faq (http://mdp.cti.depaul.edu/AlterEgo/default/

> > show/140) then tried to accesshttps://127.0.0.1:8888/admin:

[airdrummer]

> server or the client?

client, i think...ffx allows you to accept a self-signed cert...

[airdrummer]

> What happens if you try getting web2py to bind to port 443 instead of

socket.error: (13, 'Permission denied')

because ports<1024 are privileged

[achipa]

Just ran into this one, but with apache, so a little followup - this
was a case where you're trying to establish an SSL connection, and
other side expects a regular http request. It had nothing to do with
the actual port or self-signedness of the cert - just mismatching the
virtualhost directives so the https ended up being served with the
wrong entry. So, if you get this error, try http:// instead of https://
(you can't have both http and https on the same port anyway) or fiddle
with https settings.

[Alexandre Miguel de Andrade Souza]

I resolved the same error creating  new server.crt and server.key

follow the instructions of

http://www.modssl.org/docs/2.8/ssl_faq.html#ToC27

and
http://www.modssl.org/docs/2.8/ssl_faq.html#cert-ownca

2008/11/4 airdrummer <airdr...@wheel.org>

--
Atenciosamente

--
=========================
Alexandre Miguel de Andrade Souza
Diretoria de Otimização de Processos do SISEMA
Secretaria de Estado de Meio Ambiente e Desenvolvimento Sustentável

[Alexandre Miguel de Andrade Souza]

And changed the ssl virtual host configuration too.

2008/12/4 Alexandre Miguel de Andrade Souza <alexand...@gmail.com>