Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- SSH - Address Already in Use
September 5, 2005, 3:32 am
rate this thread
I posted a message eariler and it has taken 6 fricken hours just to
find the damn error message.
When I try and start SSHD I get this:
Sep 4 21:55:54 localhost sshd: fatal: Cannot bind any address.
Sep 4 22:13:07 localhost sshd: error: Bind to port 443 on
0.0.0.0 failed: Address already in use.
Sep 4 22:13:07 localhost sshd: fatal: Cannot bind any address.
A netstat command gives me this:
[root@localhost sysconfig]# netstat -ntl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
tcp 0 0 0.0.0.0:32768 0.0.0.0:*
tcp 0 0 127.0.0.1:32769 0.0.0.0:*
tcp 0 0 0.0.0.0:3306 0.0.0.0:*
tcp 0 0 0.0.0.0:110 0.0.0.0:*
tcp 0 0 0.0.0.0:111 0.0.0.0:*
tcp 0 0 0.0.0.0:6000 0.0.0.0:*
tcp 0 0 0.0.0.0:80 0.0.0.0:*
tcp 0 0 127.0.0.1:631 0.0.0.0:*
tcp 0 0 127.0.0.1:25 0.0.0.0:*
tcp 0 0 0.0.0.0:443 0.0.0.0:*
What could be wrong here??? I'm going CRAZY!!!!
- Richard E. Silverman
September 5, 2005, 5:38 am
Re: SSH - Address Already in Use
Something else is listening on port 443, so sshd can't start with the
configuration you gave it. Port 443 is normally used for https, so it
might be your web server (or maybe an existing instance of sshd). Find
out what process is listening on 443, e.g.:
# lsof -ni tcp:443
There's something else going on, though, since you get "no route to host"
when trying to SSH to port 443. You have something listening on 443, so
that shouldn't happen -- it should connect and then give a protocol error
if there were, say, a web server there instead. It's also odd that you
say SSH to port 22 does work -- since there's nothing listening on port 22
on this box. Do you have a firewall (either on this box or elsewhere)
that might be redirecting connections?
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum