by qaza » Sat, 14 Dec 2002 15:06:21
I have setup a 'main' apache which listen to port 80.
And setup another copy of apache+modssl listen to port 443, this
apache+modssl failed to start .?!
Error message: "/bin/apachectl start: httpd (pid 76190) already
running"
Error saying that the 'main' apache is running so this apache+modssl
cannot be started..?
Any idea?
Thanks
-qaz
by Aaro » Sun, 15 Dec 2002 15:01:52
Try that, it should work.
-Aaron
> I have setup a 'main' apache which listen to port 80.
> And setup another copy of apache+modssl listen to port 443, this
> apache+modssl failed to start .?!
> Error message: "/bin/apachectl start: httpd (pid 76190) already
> running"
> Error saying that the 'main' apache is running so this apache+modssl
> cannot be started..?
> Any idea?
> Thanks
> -qaz
by qaza » Wed, 18 Dec 2002 16:37:43
Using, "/bin/apachectl startssl", password correctly entered.
same problems occured, error message "httpd (pid 76190) already running"
-qaz
> Try that, it should work.
> -Aaron
> > Hi,
> > I have setup a 'main' apache which listen to port 80.
> > And setup another copy of apache+modssl listen to port 443, this
> > apache+modssl failed to start .?!
> > Error message: "/bin/apachectl start: httpd (pid 76190) already
> > running"
> > Error saying that the 'main' apache is running so this apache+modssl
> > cannot be started..?
> > Any idea?
> > Thanks
> > -qaz
by Juha Laih » Thu, 19 Dec 2002 03:57:01
You'll need two distinct apachectl scripts; I recall the name of the PIDQuote:>Using, "/bin/apachectl startssl", password correctly entered.
>same problems occured, error message "httpd (pid 76190) already running"
1. Apache on both port 80 and port 443: have to manually duplicate all directives?
Hello. I'm trying to set up my Apache 2 / mod_ssl server to respond
to both HTTP on port 80 and HTTPS on port 443.
At least at the present, I'm not making any restrictions as to what
URLs can be visited with or without SSL on.
However, I have a lot of <Location>s, Redirects, and other directives
in my port 80 VirtualHost entry. It looks like I have to manually
duplicate all these in the port 443 VirtualHost, and be careful any
time I change one to change both?? This really sucks.
I wish there was a way to set up a single VirtualHost entry that
listens to both port 80 and port 443. When I tried this with
<VirtualHost _default_:*>, it complained when I tried to fetch
documents that I was trying to speak HTTP on an SSL-enabled port.
It does appear that a workaround for most of the directives would be
to just specify them in the main_server area, in which case they apply
to all of the virtual hosts. However, this won't work for me because
I'm also running a second named-based virtual host on the machine
(that listens only to port 80).
I only want the directives to apply to my main virtual host, on both
port 80 and port 443, not to all virtual hosts on the machine.
Assuming that there's no solution to the above, and I have to just
copy and paste all my directives from my main VirtualHost section into
the :443 section, is it okay to specify the same log files in each?
Is locking done to prevent overlapping log entries if port 80 and port
443 are accessed simultaneously? Or am I required to use different
logs for each port?
Discussion of the above issues in the documentation could really stand
to be improved...
--
Dan Harkless
http://harkless.org/dan/
3. apache 1.3.6: won't listen to port 443
5. server not listening on port 443
7. Help with Apache SSL setup for ports 80 and 443
8. Linux Security Week - October 9th, 2000
9. Apache won't listen to ports other than 80
10. How to make Apache to treat port 443 as a normal port (not ssl)
11. want ssl, httpd starts, but nothing listening on port 443
12. How to listen only on port 443
13. Running Apache on port 80 in Standalone mode?