I have changed my sshd port to for e.g 2345

When I start ssh I get the following message in logs:-

Mar 12 15:13:35 srv01 sshd[2654]: error: Bind to port 2345 on 0.0.0.0 failed: Address already in use.


Has anyone have any ideas what the problem is and a fix.

Thanks

Something is already bound to 2345 on one of your IPs.

Try netstat -n |grep ':2345'

I just tried what you suggested and nothing is on that port, really puzzled over this one... :confused:

I am having a few other errors since changing the port so while I continue to investigate the other errors I have changed the ssh port back to 22, I guess plesk 7.5 doesn't really like the port to be changed. just wish swsoft would let us change the plesk internals to suite our needs.

Having changed the port back to 22 I am still getting the same error as above but now listing port 22 ?????

error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

Strange.

Are you trying to do this via Plesk itself? How are you accessing the server currently?

Are you talking about Plesk's per-client SSH support? If so I should probably keep my mouth shut because I don't allow clients to shell in. Making my changes directly to sshd_config was a pretty straight foward process. (I did it to hide shhd...non-standard port on an IP that isn't bound to any other services).

I was making the port change in sshd_config directly, yes straight forward, but keep seeing these errors in my logs, no matter what port I select.

Errors are even when I use the standard port 22

The ports mentioned in this forum are only example not the ones I try to use.

I would prefer not to let my clients have any access via ssh, but then my clients would all be using FTP and has the increased risk of a sniffer getting the passwords. I want my clients to be able to SFTP. but in a chrooted level only.

are your restarting ssh after you make the changes, no offense just asking because when you say you start, i'm not sure if you mean the ssh client or the ssh service, even though it shouldn't be in your server logs if its the client

Yes sure but not just restarting sshd, I think its better to stop and then start again

i changed mine a couple of times just to see what would happen and everything came up roses so its not the fact of it being plesk

Mar 13 21:23:59 www sshd[25759]: Server listening on 0.0.0.0 port 1352.

Mar 13 21:25:16 www sshd[30569]: Accepted password for root from xxx.xxx.xxx.xxx port 33416 ssh2

Mar 13 21:28:02 www sshd[3076]: Server listening on 0.0.0.0 port 1351.

Mar 13 21:28:24 www sshd[3080]: Accepted password for root from xxx.xxx.xxx.xxx port 33641 ssh2

I didn't have this problem when I was running EnsimPro, but then again I had many different problems with Ensim.

I suspect it could be a problem when the server was re-imaged to Plesk, I know Ev1 had problems with the re-imaging. I just really don't know why I am getting these errors, it seems Ev1 don't know either.

to change the sshd port, do this exactly!

make the change to /etc/ssh/sshd_config

then do
/etc/init.d/sshd restart

it wont disconnect your shell... but it will if u do stop then start....

if it says bind address already in use do

netstat -lnp

and look at what program is using that open port...


If you have any more problems, feel free to pm me.

what version of ssh are you using, i'm using

version 3.9p1-2.rhel3.art

I have just checked my logs again for today, and I think its all working ok now, maybe Ev1 fixed it I know they have been working on a few problems with the re-imaging because I was getting many different errors in the logs, for spamd, sshd,mailman,qmail, etc.

I will check again tomorrow.

Having too many problems with Plesk, so I have decided to move to EnsimPro on Enterprise 4.

At last everything setup and no errors except (suprise suprise)

Mar 14 23:27:56 srv01 sshd[3107]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

I Think it is something with Enterprise 4 only..

Here is Ev1's reply to the problem.

WebTech
Dear customer, sshd has been restarted and is only accepting connections with protocol 2. % ssh -1 admin@111.111.111.111
Protocol major versions differ: 1 vs. 2

The error appears to be related to IPV6, sshd itself appears to be operating properly, and the sshd configuration file is correct.

:confused: So does this mean that everything is fine and I should not worry abaut this error message? :confused: