Comments on: Problems Getting SSL Working

By: majnoona

majnoona — Tue, 07 Jul 2009 23:58:12 +0000

You seem to be the only one in the whole internet who knows how to fix this — thank you for sharing! (now just need this to work it's way up to the first Google result ;-)

By: majnoona

majnoona — Tue, 07 Jul 2009 18:58:12 +0000

You seem to be the only one in the whole internet who knows how to fix this — thank you for sharing! (now just need this to work it's way up to the first Google result ;-)

By: creeva

creeva — Tue, 09 Jun 2009 12:45:56 +0000

I didn't realize that you needed a dedicated IP either (or use the long ass directory path which is what I do for my SSL side). So that's great information. Ironic that I understand the SSL handshake and the protocol but didn't grasp that more fully.

The problem is the error is too ambiguous – so yes I do hope that your comment does help someone – thanks for leaving it.

By: Raam Dev

Raam Dev — Tue, 09 Jun 2009 06:20:19 +0000

I found this post searching Google for "ssl_error_rx_record_too_long". Here's my situation and how I eventually fixed it (I run my own web host, so I have access to WHM and cPanel):

A customer purchased and installed a certificate through cPanel, however he did not realize that he needed a dedicated IP address.

When I changed his domain to use a dedicated IP address, the SSL error "ssl_error_rx_record_too_long" was displayed in the browser when he tried accessing https://domain.com.

The problem was that when changing the domain to use a dedicated IP through WHM, the Apache Virtual Hosts entry gets reset and no longer contains the configuration for the SSL certificate.

The solution was for me to reinstall the certificate using WHM: "WHM -> SSL/TLS -> Install a SSL Certificate and Setup the Domain", then enter the domain in the Domain field and press Tab. WHM should search for the existing SSL Certificate for that domain and upon finding it, fill out all the fields on the page. Then simply press Submit to reinstall the certificate on the new dedicated IP address. After doing this, everything worked fine.

Hope this helps someone!

By: creeva

creeva — Fri, 06 Mar 2009 05:02:12 +0000

I would say you need the full path to the directory on your server - email
me at creeva (at) gmail.com and I can get a bit more in depth.

By: Chrisko

Chrisko — Thu, 05 Mar 2009 08:39:05 +0000

Great post! Exactly what I was looking for, but I have access to Web Host Manager. Is there any information you could give me in order to get mine working? Having the same problem, have spent all day on it.

By: Chrisko

Chrisko — Thu, 05 Mar 2009 07:03:37 +0000

What a great post! You are having exactly the same problem as I am, same error message and all. The only difference is the web admin has given me access to WHM (WebHost Manager), any pointers as to what I do now?

Is it essential that I have a static Ip also?

By: Eric James

Eric James — Sat, 28 Feb 2009 00:27:21 +0000

I stumbled on this page while searching for a specific TLS error code… but since I'm here I figured I'd comment

The simple answer to everything is ….You need to find a new host. As a Server Admin for a hosting company I'm amazed when I see blog after blog of things like this and the people (like you) just stay there anyway. Usually it's that people will put up with crappy support and techs that don't really speak or understand simple English because it's cheap. I'm not saying that this is why you stay there… but if it is or if price is a major factor on where you host… then in my opinion you really need to understand that you get what you pay for.

That's my 2 cents

By: creeva

creeva — Fri, 20 Feb 2009 13:15:28 +0000

My thoughts – have you removed your root certificates from your browser? Have you tried a different browser? If it's still not working to any sites after trying a different browser – your ISP maybe doing something strange upstream to your https traffic.

By: stephen

stephen — Fri, 20 Feb 2009 05:11:41 +0000

haha, and now I'm here after googling to solve the ssl_error_rx_record_too_long error as I get it for all SSL sites….guess it is not going to be so easy…

By: creeva

creeva — Mon, 09 Feb 2009 16:26:09 +0000

wanted to add – SSL is now working greast

By: creeva

creeva — Fri, 06 Feb 2009 17:32:55 +0000

Well they had it so I could connect via SSL – but the SSL site wasn't linked correctly to the HTTP site – I updated the ticket with that information – now 30 minutes later the HTTPS stops working – grrrrrrr