Home / server / Questions / 1007433
Accepted
sogu
Asked: 2020-03-19 09:40:13 +0800 CST

Digital Ocean server SSH login fault

  • 772

What I have done

  1. created a new digital ocean droplet and
  2. Created SSH key based on this guide and during the creation of the droplet I have copied it in
  3. I have run the following codes from here
ssh root@your_server_ip
adduser sammy
usermod -aG sudo sammy
  1. Than I have tried to log in as "sammy"
ssh sammy@your_server_ip

ERROR

  • Permission denied (publickey).
  • If I log in with root access than there is no problem I get in like before

Fixes I have tried

  1. cleaned put the shh key folder and only have this key there
  2. I haven't found any answer but my problem is kind of like this
  3. this is not that similar to this.
  4. ssh -vvv root@my_ip from here it pushes out like lines of debug what should I look for?
  5. I have tried to read sshd server logs on ubuntu this most common messages
Disconnected from invalid user somefirstname43
Disconnected from invalid user someotherfirstname334
Disconnected from authenticating user root
Received disconnect from ID port ...
Accepted publickey for root from ID
Did not receive identification string from  ID port ....
Connection closed by authenticating user sammy ID port portnumber  <<----
ubuntu ssh digital-ocean

2 Answers

  1. Your user sammy needs the public key you used to login to the root user. The easiest way is to copy the authorized_keys file from your root user.

    mkdir ~sammy/.ssh
chmod 640 ~sammy/.ssh
cp ~/.ssh/authorized_keys ~sammy/.ssh/
chown -R sammy:sammy ~sammy/.ssh/
    • 2
  2. Best Answer

    There is an answer for this on Digital Ocean

    1.Log in as root ssh root@IP

    2.Edit ssh config: sudo nano /etc/ssh/sshd_config

    3.Change this line: PasswordAuthentication no to PasswordAuthentication yes

    4.Restart daemon: sudo systemctl restart sshd

    5.Do ssh-copy-id: ssh-copy-id someuser@IP (if you already have a key there it may not allow you to copy so just skip this step and log in with the next step)

    6.Log in as the new superuser you have created before ssh someuser@IP

    7.Revert changes to ssh_config if you are security conscious and restart daemon.

    • 0