Trjtdtk

MaTeX, font size, and PlotLegends

Can criminal fraud exist without damages?

Have I saved too much for retirement so far?

How does residential electricity work?

Why "be dealt cards" rather than "be dealing cards"?

Minimal reference content

Can I convert a rim brake wheel to a disc brake wheel?

Implement the Thanos sorting algorithm

What defines a dissertation?

Is there an Impartial Brexit Deal comparison site?

If a character can use a +X magic weapon as a spellcasting focus, does it add the bonus to spell attacks or spell save DCs?

What is the oldest known work of fiction?

Is exact Kanji stroke length important?

What's the purpose of "true" in bash "if sudo true; then"

How will losing mobility of one hand affect my career as a programmer?

Everything Bob says is false. How does he get people to trust him?

Teaching indefinite integrals that require special-casing

At which point does a character regain all their Hit Dice?

Best way to store options for panels

Is there any reason not to eat food that's been dropped on the surface of the moon?

Print name if parameter passed to function

How could Frankenstein get the parts for his _second_ creature?

How do I rename a LINUX host without needing to reboot for the rename to take effect?

Bash method for viewing beginning and end of file

SSH to droplet with non root user

SSH doesn't ask for password, gives “permission denied” immediatelySSH keys fail for one userChanging copssh default FTP root breaks RSA authenticationAWS Amazon EC2 - password-less SSH login for non-root users using PEM keypairsVMware ESXi 4.1: how to create a new user with root permissionsChrooted user can't login with SSHOne-liner to create UNIX user, add in SSH key, disable root over SSHcan' t access ec2 instance for additional user with sftp or ssh - key refusedCreating a new user with SSH access on ec2Ubuntu 16.04 - Login not working in external SSH Clients

1

I recently made some new users in my digitalocean droplet, and I would like to access them directly with the command ssh username@ip. However, I get denied with username@ip: Permission denied (publickey). For clarification, the machine has the correct private-key and can access the droplet with ssh root@ip

I did the following to create the new user

root@school:~# adduser username
Adding user `username' ...
Adding new group `username' (1001) ...
Adding new user `username' (1001) with group `username' ...
Creating home directory `/home/username' ...
Copying files from `/etc/skel' ...
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully

After these steps, what is further to do to be able to access the droplet with ssh username@ip ?

ssh

share|improve this question

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  if available you could use the tool ssh-copy-id username@ip to copy the PUBLIC key to the authorized_key file from the user on the server
  
  – Dennis Nolte
  Mar 20 at 16:44
  

  
  
  
  

add a comment | 

1

I recently made some new users in my digitalocean droplet, and I would like to access them directly with the command ssh username@ip. However, I get denied with username@ip: Permission denied (publickey). For clarification, the machine has the correct private-key and can access the droplet with ssh root@ip

I did the following to create the new user

root@school:~# adduser username
Adding user `username' ...
Adding new group `username' (1001) ...
Adding new user `username' (1001) with group `username' ...
Creating home directory `/home/username' ...
Copying files from `/etc/skel' ...
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully

After these steps, what is further to do to be able to access the droplet with ssh username@ip ?

ssh

share|improve this question

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  if available you could use the tool ssh-copy-id username@ip to copy the PUBLIC key to the authorized_key file from the user on the server
  
  – Dennis Nolte
  Mar 20 at 16:44
  

  
  
  
  

add a comment | 

I recently made some new users in my digitalocean droplet, and I would like to access them directly with the command ssh username@ip. However, I get denied with username@ip: Permission denied (publickey). For clarification, the machine has the correct private-key and can access the droplet with ssh root@ip

I did the following to create the new user

root@school:~# adduser username
Adding user `username' ...
Adding new group `username' (1001) ...
Adding new user `username' (1001) with group `username' ...
Creating home directory `/home/username' ...
Copying files from `/etc/skel' ...
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully

After these steps, what is further to do to be able to access the droplet with ssh username@ip ?

ssh

share|improve this question

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

root@school:~# adduser username
Adding user `username' ...
Adding new group `username' (1001) ...
Adding new user `username' (1001) with group `username' ...
Creating home directory `/home/username' ...
Copying files from `/etc/skel' ...
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully

share|improve this question

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

New contributor

Jonas Grønbek is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked Mar 20 at 13:08

Jonas GrønbekJonas Grønbek

1084

1 Answer
1

active

oldest

votes

5

"the machine has the correct private-key"

That is the root cause of your misunderstanding. Access is controlled separately for each account, not for the machine as a whole.

For each account you want to access with a particular key you will need to append the associated public key to the file ~/.ssh/authorized_keys in the home directory of that account.

Or in other words: copy /root/.ssh/authorized_keys to /home/username/.ssh/authorized_keys and ensure the correct ownership and permissions on those files/directories.

share|improve this answer

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  while true please note that you will copy the PUBLIC key, not the private key into the authorized_keys. Additionally copy might just overwrite and give too much access so be catious when doing a copy.
  
  – Dennis Nolte
  Mar 20 at 16:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  Mar 21 at 14:21
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @JucaPirama ssh-copy-id user@remote-host leaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
  
  – HBruijn
  Mar 21 at 14:30
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

Jonas Grønbek is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f959119%2fssh-to-droplet-with-non-root-user%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

5

"the machine has the correct private-key"

That is the root cause of your misunderstanding. Access is controlled separately for each account, not for the machine as a whole.

For each account you want to access with a particular key you will need to append the associated public key to the file ~/.ssh/authorized_keys in the home directory of that account.

Or in other words: copy /root/.ssh/authorized_keys to /home/username/.ssh/authorized_keys and ensure the correct ownership and permissions on those files/directories.

share|improve this answer

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  while true please note that you will copy the PUBLIC key, not the private key into the authorized_keys. Additionally copy might just overwrite and give too much access so be catious when doing a copy.
  
  – Dennis Nolte
  Mar 20 at 16:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  Mar 21 at 14:21
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @JucaPirama ssh-copy-id user@remote-host leaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
  
  – HBruijn
  Mar 21 at 14:30
  

  
  
  
  

add a comment | 

5

"the machine has the correct private-key"

That is the root cause of your misunderstanding. Access is controlled separately for each account, not for the machine as a whole.

For each account you want to access with a particular key you will need to append the associated public key to the file ~/.ssh/authorized_keys in the home directory of that account.

Or in other words: copy /root/.ssh/authorized_keys to /home/username/.ssh/authorized_keys and ensure the correct ownership and permissions on those files/directories.

share|improve this answer

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  while true please note that you will copy the PUBLIC key, not the private key into the authorized_keys. Additionally copy might just overwrite and give too much access so be catious when doing a copy.
  
  – Dennis Nolte
  Mar 20 at 16:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  Mar 21 at 14:21
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @JucaPirama ssh-copy-id user@remote-host leaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
  
  – HBruijn
  Mar 21 at 14:30
  

  
  
  
  

add a comment | 

"the machine has the correct private-key"

That is the root cause of your misunderstanding. Access is controlled separately for each account, not for the machine as a whole.

For each account you want to access with a particular key you will need to append the associated public key to the file ~/.ssh/authorized_keys in the home directory of that account.

Or in other words: copy /root/.ssh/authorized_keys to /home/username/.ssh/authorized_keys and ensure the correct ownership and permissions on those files/directories.

share|improve this answer

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

share|improve this answer

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149

answered Mar 20 at 13:20

HBruijnHBruijn

55.7k1190149