SSL ssl_error_rx_record_too_long

[nmpribeiro]

So...

I've started running into this error...

Secure Connection Failed

An error occurred during a connection to lavoulp.com. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

All domains have this problem, must be the SSL i've generated.

The SSL is the same for kloxo, however, it works fine in kloxo (is it some diference between kloxo's https protocol and httpd?)

I need some enlightment here please,
Thanks in advance...

[MRatWork]

Try using 'self assign' ssl and then compare to your ssl.

[nmpribeiro]

Hi MR,

I don't own an ssl cert. All certs I have were "self assigned", or created in Kloxo interface. Doesn't matter if I use domain I own, or www.domain or a key with 2048 or less. Works on https://kloxo:777 (I've checked it's the one I've generated in kloxo Interface) but... domains I have do not work on 443 (they show the error I've specified priviously)

[nmpribeiro]

So... I've switched programs from apache to nginx

All working now

but... damn!... can anyone else replicate this issue?

nginx seams very fast so I'll stick with it and not dig the problem any further

[MRatWork]

I didn't found this issue for apache and hiawatha-proxy (using Kloxo-MR 6.5.1).

[nmpribeiro]

Hum... yes, it's strange. I'm moving back to apachce. Nginx didn't let css and js files go with https so I'll try to understand the problem.

So... apache now has a problem... (I seam to be bumping into all of them)

Fixed ssl cert by assigning to the domain name the actual "server1.domainname.com" info. That was the problem

No, if I try to access my server through http, I get a "The connection was reset" while if I go through https, it asks me if I want to accept it and then gives the same result as in http.

[nmpribeiro]

Going back to apache, I've figured out I needed to re-install the php components (php54 in my case) and fix the php-fmp

Now all is great

Guess if I share insights someone will figure this out also