SSL_ERROR_RX_RECORD_TOO_LOG message after fresh server install on Ubuntu 14.04

By: Matthew Wicks user 28 Sep 2015 at 1 p.m. CDT

9 Responses
Matthew Wicks gravatar
I am very new to Gluu and just trying to get a server setup so that I can try it out but I am having trouble getting it working. I setup a new install of gluu on Ubuntu based on the instructions (http://www.gluu.org/docs/admin-guide/deployment/ubuntu/) everything installed fine but when I attempt to connect to https://localhost or https://ce.gluu.info or https://[IP], I get an error: SSL_ERROR_RX_RECORD_TOO_LOG I have accepted all the defaults on the install. Anyone have any suggestions?
None
closed

Answers

By Michael Schwartz Account Admin 28 Sep 2015 at 1:42 p.m. CDT

Copy
Michael Schwartz gravatar
You can't use localhost. You must use a hostname. I suggest using something like idp.deltaware.com and then making sure this hostname is in your local computer and the host system.

By Matthew Wicks user 29 Sep 2015 at 11:15 a.m. CDT

Copy
Matthew Wicks gravatar
I tried a few different host names including the default one (ce.gluu.info), the one you suggested (idp.deltaware.com) as well the original name of the VM I was using, and they all gave me the same SSL_ERROR_RX_RECORD_TOO_LOG error. I also tried going to http://[host] (aka no ssl) and this provided me with a standard apache folder structure html page, with an html folder. http://[host]:443 gives the same results as http://[host]:80 so it kind of looks like ssl is not turned on at the apache level. any ideas what I'm doing wrong?

By Aliaksandr Samuseu staff 29 Sep 2015 at 1:03 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Matthew. First of all, >I tried a few different host names including the default one You should be using the one you provided to the setup.py script during initial configuration. If it was the default one, it should be "ce.gluu.info". You also should verity that at least inside chroot-ed container your hostname is actually set to this string. A few questions: 1) Does your machine meet Gluu's minimal requirements (i.e. it must has at least 2,5-3GB of RAM, and has a 64bit OS installed)? 2) Is your browser updated to the most recent version available? Have you tried to access your Gluu instance with some other browser? Does it have any 3rd-party security-related add-ons installed? Do you have any anti-virus solution installed on the machine from which you are accessing Gluu's box, which tries to filter web traffic? Regards, Alex.

By Aliaksandr Samuseu staff 29 Sep 2015 at 1:05 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
A quick addition: if you are accessing Gluu from the same host it's installed in, and as you are using non-resolvable name for it, you also must verify that there is a record for it in /etc/hosts file, or you browser won't be able to transform it into ip address.

By Aliaksandr Samuseu staff 29 Sep 2015 at 1:29 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
> I also tried going to http://[host] (aka no ssl) and this provided me with a standard apache folder structure html page, with an html folder. I missed that one, sorry. That doesn't seem good. Even not fully-functional instance of Gluu usually at least redirects you to the url with https://[..] scheme. Something is seriously wrong with your installation.

By Matthew Wicks user 29 Sep 2015 at 2:20 p.m. CDT

Copy
Matthew Wicks gravatar
Think I got this working. I had to change the /etc/apache2/sites-available/https-gluu.conf I removed the IP addresses in the <VirtualHost [IP]:80>... & <VirtualHost [IP]:443>... and replaced them with <VirtualHost *:80>... & <VirtualHost *:443>...

By Aliaksandr Samuseu staff 29 Sep 2015 at 3:35 p.m. CDT

Copy
Aliaksandr Samuseu gravatar
> I removed the IP addresses in the <VirtualHost [IP]:80>... & <VirtualHost [IP]:443>... and replaced them with > <VirtualHost *:80>... & <VirtualHost *:443>... Do you have it installed at some cloud-hosted vm? AFAIK, our guide for cloud installation contains such recommendations. If it's the case, can I ask which cloud service are you using?

By Matthew Wicks user 30 Sep 2015 at 7:05 a.m. CDT

Copy
Matthew Wicks gravatar
I have my server setup on a VM locally so not a cloud install but I am using hyperV for my VM's so maybe the fact that I am using a VM instead of a physical machine could be requiring this? thanks for you help on this.

By Aliaksandr Samuseu staff 30 Sep 2015 at 9:43 a.m. CDT

Copy
Aliaksandr Samuseu gravatar
Np, you are welcome. >I am using hyperV for my VM's so maybe the fact that I am using a VM instead of a physical machine could be requiring this That shouldn't be, at least I never had had to modify any configs on my vms just to access its web UI. May I ask what kind of network layout are you using? Were you accessing it through some kind of port forwarding, by any chance? It's often the case when connecting to local vm from a physical machine, if you are keeping vms in a separate virtual network.

Post an answer