Yes, I do have one other Listen directive...the Listen my.ip:80 for http, and
yes, it is outside all virtual host directives, because as far as I am aware,
they have to be. I tried placing them inside virt host directives and I got a
config error. I have no BindAddress directives at all, and
Hi Terry,
Perhaps your directives are being overridden in a IfDefine SSL or
IfModule SSL block ? Listen IP:Port does work, works for me. Do you
have the following in your config ?
Listen my.ip.address:443
...
NameVirtualHost my.ip.address:443
...
VirtualHost my.ip.address:443
...
/VirtualHost
On Thu, 6 Mar 2003, Terry Kerr wrote:
Hi,
I am running apache 1.3.26 and mod_ssl 2.8.9-2.1 on a debian linux system.
The system has two IP's, and I only wish for apache to start on ports 80 and 443
on one of those IPs. I am using named based virtual hosting for many sites on
the
Mark,
Thanks for you suggestion, but whenever I try to put
Listen my.ip.address:443 (with the correct ip address ;-)
My http or https server does start at all on any port. The log error I get is
[crit] (98)Address already in use: make_sock: could not bind to address
203.89.254.243 port 443
it sounds like perhaps yer http.conf files have perhaps more then one
listen directive, perhaps outside the virtual Host directives. Might
try grepping the file for listen and see what comes up. or, better yet,
egrepping for bind|listen|etc...
thanks,
Ron DuFresne
On Fri, 7 Mar 2003, Terry
my apologies...I am an idiot...I found the other Listen directive ;-)
terry
R. DuFresne wrote:
it sounds like perhaps yer http.conf files have perhaps more then one
listen directive, perhaps outside the virtual Host directives. Might
try grepping the file for listen and see what comes up. or,
Hi,
I am running apache 1.3.26 and mod_ssl 2.8.9-2.1 on a debian linux system.
The system has two IP's, and I only wish for apache to start on ports 80 and 443
on one of those IPs. I am using named based virtual hosting for many sites on
the system for http, and have just one virtual host
