apache2: ssl_error_rx_record_too_long when visiting port 80? help!
Posted
by
John
on Server Fault
See other posts from Server Fault
or by John
Published on 2011-01-14T18:52:57Z
Indexed on
2011/01/14
18:54 UTC
Read the original article
Hit count: 497
Hi,
I have an Ubuntu 10 x64 server edition machine. I got a second IP and configured /etc/network/interfaces like so (actual IPs and gateways removed):
[code] auto lo iface lo inet loopback
iface eth0 inet dhcp
auto eth0 auto eth0:0
iface eth0 inet static address [ my first IP ] netmask 255.255.255.0 gateway [ my first gateway ]
iface eth0:0 inet static address [ my second IP ] netmask 255.255.255.0 gateway [ my second gateway ] [/code]
/etc/apache2/ports.conf:
[code] Listen 80 NameVirtualHost [ my first IP ]:80 NameVirtualHost [ my second IP ]:80
# If you add NameVirtualHost *:443 here, you will also have to change # the VirtualHost statement in /etc/apache2/sites-available/default-ssl # to # Server Name Indication for SSL named virtual hosts is currently not # supported by MSIE on Windows XP. Listen 443 NameVirtualHost [ my first IP - some site is running SSL successfully using it ]:443
Listen 443 [/code]
/etc/apache2/sites-enabled/mysite.conf:
[code] ServerName mysite.com Include /var/www/mysite.com/djangoproject/apache/django.conf [/conf] [/code]
Then when visiting http[mysite].com:80 or http[mysite].com (:// removed because serverfault doesn't allow me to post hyperlinks), I get:
[code] An error occurred during a connection to [mysite].com.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long) [/code]
My guess is that the configuration file is not being picked up, and apache is therefore looking for the default-ssl file, which is not in conf-enabled. If I were to configure that file properly, it seems I would successfully connect to whatever default directory is specified in the default-ssl file. But I want to connect to my website.
Any ideas?
Thanks in advance!
© Server Fault or respective owner