Hello all,
I have downloaded and installed Apache 2.0.35 with SSL. I have configured
the httpd.conf as they suggest in ssl.conf. However, when i try to start
apachectl i get the following message:
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:443
no listening sockets
You're not trying to run two httpd's on the same set of ports are you, the
old one running while trying to fire up the new?
that's what the error suggests I think...
thanks,
Ron DuFresne
On Mon, 15 Apr 2002, paul priestman wrote:
Hello all,
I have downloaded and installed Apache 2.0.35
paul priestman wrote:
Hello all,
I have downloaded and installed Apache 2.0.35 with SSL. I have configured
the httpd.conf as they suggest in ssl.conf. However, when i try to start
apachectl i get the following message:
(13)Permission denied: make_sock: could not bind to address
(13)Permission denied: make_sock: could not bind to address
0.0.0.0:443
no listening sockets available, shutting down
./apachectl startssl: httpd could not be started
It's *not* trying to start on 8443 though...
thanks,
Ron DuFresne
On Mon, 15 Apr 2002, paul priestman wrote:
i'm
There is 2 reason for not being able to bind to a port. One, another
process already has it open and is currently listen (netstat -a or
under linux netstat -vatp). Two, you have to be root to bind to ports
under 1024.
Jeremy Walton
DICE Corporation
-Original Message-
From: [EMAIL
i'm actually trying to run this server on port 8443 - the other httpd runs
on port 443 but i have stopped this server running (as its just another test
server). I am starting the server as my self - not as root but the port is
1024 anyway
I have tried chaning the port to other numbers
Dear Paul,
RE:(13)Permission denied: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down AND I have tried changing the
port
to other numbers as well but to no luck
---
Just a thought... can you ping to that IP address of 0.0.0.0? And
0.0.0.0 tells the OS to bind to all network adapters. Its not really a
usable IP address.
Jeremy Walton
DICE Corporation
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Andrew Lietzow
Sent: Monday, April 15, 2002 10:27 AM
To: [EMAIL PROTECTED]
So its trying to bind to 443 - i have stated in my ssl.conf to listen on
port 8443 and have set up a virtual host for port 8443 with ssl enabled -
how come it tries to bind to port 443?
I have therefore tried to start the server as root - it started okay but I
cannot make a ssl connection - i
It's fixed in Apache's CVS version. See bugzilla bug 7802
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7802)
Issac
__
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List
I've just upgraded my front-end server to Apache
2.0.35/mod_ssl/openssl-0.9.6b When I try to connect to an https
virtualhost, however, the connection just seems to hang there. Now, the
backend is NOT running mod_ssl (under Apache 1.3, it didn't have to).
Does it have to, now? the
paul priestman wrote:
So its trying to bind to 443 - i have stated in my ssl.conf to listen on
port 8443 and have set up a virtual host for port 8443 with ssl enabled -
how come it tries to bind to port 443?
I have therefore tried to start the server as root - it started okay but I
Hello Jeremy,
RE:: 0.0.0.0 tells the OS to bind to all network adapters. Its not really
a
usable IP address.
Maybe this is a bit off subject, but doesn't the Apache web server have to
bind to a specific network interface? If you are trying to have it listen
for packets on 443 or 8443,
On Mon, Apr 15, 2002 at 11:48:33AM +0300, Issac Goldstand wrote:
I've just upgraded my front-end server to Apache
2.0.35/mod_ssl/openssl-0.9.6b When I try to connect to an https
virtualhost, however, the connection just seems to hang there. Now, the
backend is NOT running mod_ssl (under
On Mon, Apr 15, 2002 at 05:18:05PM +0200, Owen Boyle wrote:
What's this about ssl.conf? Are you including this file into
httpd.conf at runtime?
This is the default for Apache2 - the ssl configuration has been
moved out of httpd.conf to ssl.conf
vh
Mads Toftum
--
With a rubber duck, one's
As owen I think mentioned, you might have to cleanup the old httpd.conf
file, it might well be trying to setup two connections on thesame port.
another suggested here it might be your config, you might not be binding
to a specific IP/NIC.
Thanks,
Ron DuFresne
On Mon, 15 Apr 2002, paul
I got that as well; I found that, while with Apache 1.3 I only needed to set
ServerName in httpd.conf, in Apache 2.0 I needed also to edit both
httpd.conf and ssl.conf and change the 0.0.0.0 in both files to my
system's real IP address (and, since I didn't care to test as root, change
the port
Dear Mads Toftum,
This is the default for Apache2 - the ssl configuration has been
moved out of httpd.conf to ssl.conf
---
And what a marvelous business/IT decision that was! I applaude
this whole-heartedly.
I am but a mere mortal, simply needing to know enough to
configure,
Actually, the capability to seperate parts of the configuration has always
been in place, it just was not the standard nor the adopted practise in
earlier apache releases. In fact, I think seperation of configuration was
dropped fairly early on in apache/modssl development as some early web
Hi Lynn,
Not having the time to deal with 2.0.** right now, I haven't been keeping an
eye on how swamp is finding it. In principle however, swamp's satisfaction
with Apache 2.0 should be roughly equivalent to that of openssl s_client.
However, if Apache 2.0 itself doesn't like the GET
20 matches
Mail list logo
