Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: ElFroggio on December 20, 2016, 11:02:32 PM
-
SME 9.1
Today I tried to log on through the web interface and it wouldn't, so I did ssh admin@192.168.1.14 and got the following message:
ssh admin@192.168.1.14
Permission denied (publickey).
When login as root I have no problem. I reset the admin password just in case. But 'no dice'.
Last login from admin was 2 days ago and it was successful and as far as I know, nothing has changed.
[froggy@dodoite ~]$ ssh -v admin@192.168.1.14
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 192.168.1.14 [192.168.1.14] port 22.
debug1: Connection established.
debug1: identity file /home/froggy/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000
debug1: Authenticating to 192.168.1.14:22 as 'admin'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: umac-64@openssh.com compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: umac-64@openssh.com compression: none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<3072<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:bQQEOvcIOPVzBDtYFpP91g/1oU6pXCuqy9Pe8+lQ4XQ
debug1: Host '192.168.1.14' is known and matches the RSA host key.
debug1: Found key in /home/froggy/.ssh/known_hosts:6
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/froggy/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/froggy/.ssh/id_dsa
debug1: Trying private key: /home/froggy/.ssh/id_ecdsa
debug1: Trying private key: /home/froggy/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
I have checked my .ssh local directory and it's identical to my previous weekly backup, when it was working
Here is root which works:
[froggy@dodoite ~]$ ssh -v root@192.168.1.14
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 192.168.1.14 [192.168.1.14] port 22.
debug1: Connection established.
debug1: identity file /home/froggy/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/froggy/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000
debug1: Authenticating to 192.168.1.14:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: umac-64@openssh.com compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: umac-64@openssh.com compression: none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<3072<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:bQQEOvcIOPVzBDtYFpP91g/1oU6pXCuqy9Pe8+lQ4XQ
debug1: Host '192.168.1.14' is known and matches the RSA host key.
debug1: Found key in /home/froggy/.ssh/known_hosts:6
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/froggy/.ssh/id_rsa <<<<<<<<<<<<<<<<<
debug1: Server accepts key: pkalg ssh-rsa blen 277 <<<<<<<<<<<<<<<<<
debug1: Authentication succeeded (publickey). <<<<<<<<<<<<<<<<<
Authenticated to 192.168.1.14 ([192.168.1.14]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
Last login: Tue Dec 20 13:48:49 2016 from pc-00071.911networks.com
************ Welcome to SME Server 9.1 *************
Before editing configuration files, familiarise
The <<<< are the difference. Why?
Thanks
Syv
-
try 'ssh root@YOURIP'
-
try 'ssh root@YOURIP'
It works.
For me the problem is the admin account. I can't connect, I can't log in through the web interface: server-manager
Thanks
Syv
-
ok..
how did you change admin's password (see your initial post)?
-
BTW, you can log in in ssh as root and then use
console
to reach the console and
elinks
to see server-manager..
-
and, finally, did you follow the wiki's advice?
https://wiki.contribs.org/SME_Server:Documentation:FAQ:Section01#Reset_the_root_and_admin_password
-
BTW, you can log in in ssh as root and then use
console
to reach the console and
elinks
to see server-manager..
Yes that work when I'm at the server console.
But I still can't logon from my computer (on the local network) to server-manager (chromium & firefox)
-
and, finally, did you follow the wiki's advice?
https://wiki.contribs.org/SME_Server:Documentation:FAQ:Section01#Reset_the_root_and_admin_password
Yes.
But I still can't logon from my computer (on the local network) to server-manager
Thanks
Syv
-
ok..
can you access server-manager from elinks?
-
ok..
can you access server-manager from elinks?
Yes at the console, no at my desk.
Which log file keeps track of the web failed/errors for signing in into server-manager?
Thanks
Syv
-
well.. elinks is a browser.. a text one, but a browser.. if you can log in in server-manager using elinks it means that authentication is working..
I guess it's something related to your client.. or to something you did..
can you give us as much details as you can, please? did you try from another client? with a different browser?
-
and, please, give us details abou
Today I tried to log on through the web interface and it wouldn't
what do you see in the browser? can you reach server-manager? if you try to authenticate, which error message do you see?
please, be verbose, we can't see your screen, we don't know anything about your server.. help us to help you, thank you
-
well.. elinks is a browser.. a text one, but a browser.. if you can log in in server-manager using elinks it means that authentication is working..
I guess it's something related to your client.. or to something you did..
can you give us as much details as you can, please? did you try from another client? with a different browser?
Here's the screen capture after trying to login as admin: http://i.imgur.com/x5FvidH.png (http://i.imgur.com/x5FvidH.png)
I do not see any error message. That's why I was asking which log file would record/debug the failure.
Tonight when I get back my laptop, I try another it on it.
Thanks
Syv