Let’s get some additional output. Clearly your client seems to be able to
connect (the error is an SSH error) but perhaps something else is not
working properly. The ssh client can give you a lot of debugging output:
ssh -vvv firstname.lastname@example.org
Of course, make sure you are not using ‘root’, or if you are that you also
change ‘PermitRootLogin’ to ‘yes’ (and uncomment it) if it is set to ‘no’.
Better yet, test with a user other than ‘root’ since you s build really
not allow direct SSH access via ‘root’ with a password.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
On Wed, 02 May 2018 16:06:02 +0000, transformers1 wrote:
> Hello There Linux specialists,
> a have set up a linux server with ssh and enabled port 22 by going in to
> the /etc/ssh/sshd_config file and changed the PasswordAuthorzed form no
> to yes.
> But when i still try to login from my client computer to the server, the
> only message i get is this: "Permission denied
> does someone know what is going on.
IIRC, you need to restart sshd in order to have changes to the config
take effect - did you restart the daemon?
I opened the port on the correct interface on the firewall.
kvm:~ # grep 'PasswordAuthentication' /etc/ssh/sshd_config
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication, then enable this but set PasswordAuthentication
From another system I was able to ssh in as root, asccept the fingerprint, and login with a password.
I could do the same as root from the localhost:
kvm:~/.ssh # ssh localhost
The authenticity of host 'localhost (127.0.0.1)' can't be established.
ECDSA key fingerprint is SHA256:jTjTrRnkeChX/euzbVHrJ7xHJ368VmKGToIVbC8oX2M.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
Last login: Thu May 3 02:37:35 2018 from 10.0.0.1
Have a lot of fun...
My guess is following the debug instructions above will show you that you have a host key issue.
I would change the value back to no and follow these instructions if it is keys:
From a query from the same poster in the Networking sub-forum (which was an installation question) this problem is probably with an MS Windows client. We are given no information about the client configuration – it could be something like trying to use a deprecated protocol.