Re: SSH - Port Conflict??
- From: syscjm@xxxxxxxxxxxxxxxxxx (Chris Mattern)
- Date: Thu, 16 Nov 2006 15:08:04 -0000
In article <1163618491.859655.320430@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
amerar@xxxxxxx wrote:
Lew Pitcher wrote:
Standard interfaces do not permit processes to bind to a port that is
already in use. Port 443 is the standard port for HTTPS, and port 80 is
the standard port for HTTP. If you have a webserver already active on
your system, it has already bound itself to port 80 and likely also
port 443. Any new program (like sshd) cannot bind to those ports
because they are already in use.
If you absolutely /must/ use port 443, shut down your webserver, or at
least disable it's use of HTTPS.
HTH
--
Lew
Hmm....why did it work in Red Hat 9.0?? Also, where do I shut down
https?
Presumably because you weren't running apache on the RH9 box, or
if you were, it wasn't set up to run https. I don't know that
much about Apache, so I can't give you much advice about what
you want to do to get it to free up the port. A lot depends
on what the Apache server is doing there; if it's actively
serving up encrypted web pages, you'll break that when you
take it off port 443.
That netstat command on my Red Hat 9.0 server gives this output:
tcp 0 0 0.0.0.0:443 0.0.0.0:*
LISTEN
tcp 0 0 192.168.1.110:443 192.108.183.4:39472
ESTABLISHED
tcp 0 0 192.168.1.110:443 192.168.1.100:4989
ESTABLISHED
tcp 0 0 192.168.1.110:443 192.108.183.4:40648
ESTABLISHED
This is the box where you're running sshd on port 443, right?
Then what you're seeing here is the sshd listening on port 443,
and three people logged on to it, two from 192.108.183.4, and
one from 192.168.1.100. You can have multiple connections
through one port, but only one process can *listen* on the port
for new connections.
--
Christopher Mattern
"Which one you figure tracked us?"
"The ugly one, sir."
"...Could you be more specific?"
.
- References:
- SSH - Port Conflict??
- From: amerar@xxxxxxx
- Re: SSH - Port Conflict??
- From: Todd H.
- Re: SSH - Port Conflict??
- From: amerar@xxxxxxx
- Re: SSH - Port Conflict??
- From: Lew Pitcher
- Re: SSH - Port Conflict??
- From: amerar@xxxxxxx
- SSH - Port Conflict??
- Prev by Date: Urgent : SSH+PLINK command length problem
- Next by Date: Key Managment
- Previous by thread: Re: SSH - Port Conflict??
- Next by thread: Re: SSH - Port Conflict??
- Index(es):
Relevant Pages
|
|