[SOLVED] Remote Manager, Port 22 issue

[uxbod]

Are you logging into the server as root or another user prior to performing the 'su' ?

[sefs]

Originally Posted by uxbod

Are you logging into the server as root or another user prior to performing the 'su' ?

I had to go

sudo -i u zimbra

because I am on ubuntu.

[sefs]

Ok I have my ssh server set up on port 22.

I can log in as a regular user and the results would be

fshlampserver@mail:~/.ssh$ ssh -v -i ~/.ssh/ssh_host_rsa_key fshlampserver@mail.fshzimbra.lan -p 22
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to mail.fshzimbra.lan [192.168.1.60] port 22.
debug1: Connection established.
debug1: identity file /home/fshlampserver/.ssh/ssh_host_rsa_key type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'mail.fshzimbra.lan' is known and matches the RSA host key.
debug1: Found key in /home/fshlampserver/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/fshlampserver/.ssh/ssh_host_rsa_key
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
Last login: Fri Jul  3 06:12:54 2009 from mail.fshzimbra.lan
fshlampserver@mail:~$ exit

So I know that the ssh server i installed prior to installing zimbra is up and working.

However no matter what I try which were
1) generating keys (dsa by default) via the zimbra user commands as mention earlier in this thread
2) generating keys the normal way (both dsa and rsa)

I cant get the test connection done by the zimbra user. The ssh server that I am using looks for authorized_keys2 as opposed to authorized_keys so I change that file name in /opt/zimbra/.ssh and all should have been good I think...

But this is how the connection goes

zimbra@mail:~/.ssh$ ssh -v -i ~/.ssh/zimbra_identity zimbra@mail.fshzimbra.lan -p 22 
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to mail.fshzimbra.lan [192.168.1.60] port 22.
debug1: Connection established.
debug1: identity file /opt/zimbra/.ssh/zimbra_identity type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'mail.fshzimbra.lan' is known and matches the RSA host key.
debug1: Found key in /opt/zimbra/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /opt/zimbra/.ssh/zimbra_identity
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

UPDATE: on checking my auth log while running the connect command I see this appear
"Jul 3 08:08:14 mail sshd[6310]: User zimbra not allowed because account is locked"

Why is it locked and should it be unlocked (and how is this done) so that we can connect and get rid of the error in the zimbra web interface. I'm on ubuntu 8.04

Thanks.


UPDATE 1:
Ok from the post Mail Queue ssh error I was able to unlock the zimbra user and now everyting is honky dory for now.

[mfinkler]

Hi everyone,

I found this post because I got the same problems and can't solve them.

zimbra@ZimbraX1:~$ ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbraY2.domain.com -p 22
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to zimbraY2.domain.com [x.x.x.x] port 22.
debug1: Connection established.
debug1: identity file .ssh/zimbra_identity type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'zimbraY2.domain.com' is known and matches the RSA host key.
debug1: Found key in /opt/zimbra/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: .ssh/zimbra_identity
debug1: Remote: Forced command: /opt/zimbra/libexec/zmrcd
debug1: Server accepts key: pkalg ssh-dss blen 434
debug1: read PEM private key done: type DSA
debug1: Remote: Forced command: /opt/zimbra/libexec/zmrcd
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = de_DE.UTF-8

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to zimbral2.zimboo.de closed.
debug1: Transferred: stdin 0, stdout 0, stderr 42 bytes in 4.4 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 9.6
debug1: Exit status 0

In this case it works!

The next one:

zimbra@ZimbraX1:~$ ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbraY1.domain.com -p 22
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to zimbraY1.domain.com [xx.xx.xx.xx] port 22.
debug1: Connection established.
debug1: identity file .ssh/zimbra_identity type 2
ssh_exchange_identification: Connection closed by remote host
zimbra@ZimbraX1:~$

Any Ideas?

Thank You!

[fulltears]

good~ now I can fix part of my problem. Thanks

[nahuelon]

Hi everybody. I had the same problem and I fix it disabling the SElinux on my Fedora. Thanks phoenix!!!

[phoenix]

Originally Posted by nahuelon

Hi everybody. I had the same problem and I fix it disabling the SElinux on my Fedora. Thanks phoenix!!!

You're welcome.

[mailman.33]

mmorse,

I had issues with mailqueue and certs broken in zimbraAdmin console, those steps worked perfectly! Thanks mmorse!! You are a pal.

[BLuesTime]

Just to let you know that we had the same problem,

I did the procedure from M. Morse " thanks " but alone did not solve all my problems. The last step I did is that I ran as root "/opt/zimbra/libexec/zmfixperms --verbose --extended" and no errors anymore.

Thanks to the Community!

[nosebreaker]

Just a FYI, for anybody that has this problem and has AllowUsers enabled in their sshd_config, you need to add the zimbra users to the this line!

I was receiving this error whenever I clicked on "Mail Queues" or other pages, and it went away as soon as I allowed zimbra to the AllowUsers line.

I want to add that I have Zimbra working (I think) with SELinux so far! (disregard, no I don't)