On 11/13/2009 12:29 PM, Philip Wigg wrote:
NameVirtualHost 192.168.1.47:443
NameVirtualHost 192.168.1.129:443
You can't use name based virtual hosting with SSL. Try these lines
out. You need to make sure you have a Listen directive for those
IP/port combinations though.
Cheers,
Phil.
On Fri, Nov 13, 2009 at 05:29:07PM +, Philip Wigg wrote:
> > NameVirtualHost 192.168.1.47:443
> > NameVirtualHost 192.168.1.129:443
>
> You can't use name based virtual hosting with SSL. Try these lines
> out. You need to make sure you have a Listen directive for those
> IP/port combinations t
On Fri, Nov 13, 2009 at 12:31:50PM -0500, Eric Covener wrote:
> >
> >
>
> > When I visit https://virtual.host2/ I get:
> >
> > SSL received a record that exceeded the maximum permissible length.
> >
> > (Error code: ssl_error_rx_record_too_long)
> >
>
> My guess is that your actually receving t
>
>
> When I visit https://virtual.host2/ I get:
>
> SSL received a record that exceeded the maximum permissible length.
>
> (Error code: ssl_error_rx_record_too_long)
>
My guess is that your actually receving this connection on an
interface not listed in any of your vhosts, so it's handled as
> NameVirtualHost 192.168.1.47:443
> NameVirtualHost 192.168.1.129:443
You can't use name based virtual hosting with SSL. Try these lines
out. You need to make sure you have a Listen directive for those
IP/port combinations though.
Cheers,
Phil.
--
I have one physical server with two IP addresses. I created
VirtualHosts for each:
NameVirtualHost 192.168.1.47:443
NameVirtualHost 192.168.1.129:443
ServerName virtual.host1
DocumentRoot /var/www/html2
ErrorLog logs/ssl_error2_log
CustomLog logs/ssl_request2_log \
"%t
