Mrthdrb

How would you translate "more" for use as an interface button?

A Trivial Diagnosis

What features enable the Su-25 Frogfoot to operate with such a wide variety of fuels?

Doesn't the system of the Supreme Court oppose justice?

How do you make your own symbol when Detexify fails?

Delete multiple columns using awk or sed

How can I, as DM, avoid the Conga Line of Death occurring when implementing some form of flanking rule?

How can I write humor as character trait?

Giving feedback to someone without sounding prejudiced

How to convince somebody that he is fit for something else, but not this job?

What to do when eye contact makes your coworker uncomfortable?

Does the Linux kernel need a file system to run?

Is there any evidence that Cleopatra and Caesarion considered fleeing to India to escape the Romans?

How to get directions in deep space?

How much theory knowledge is actually used while playing?

Why should universal income be universal?

Why is the Sun approximated as a black body at ~ 5800 K?

How do I tell my boss that I'm quitting soon, especially given that a colleague just left this week

Mimic lecturing on blackboard, facing audience

The Digit Triangles

awk assign to multiple variables at once

How to make money from a browser who sees 5 seconds into the future of any web page?

Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?

Shouldn’t conservatives embrace universal basic income?

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 yesterday

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
  yesterday
  

  
  
  
  

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 yesterday

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
  yesterday
  

  
  
  
  

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 yesterday

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 yesterday

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 yesterday

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 yesterday

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 yesterday

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 yesterday

HBruijnHBruijn

55.5k1090149

• 
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  11 hours ago
  

  
  
  
  

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 yesterday

HBruijnHBruijn

55.5k1090149

• 
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  11 hours ago
  

  
  
  
  

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 yesterday

HBruijnHBruijn

55.5k1090149

• 
  
  
  

  
  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
  yesterday
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It would be simpler using the ssh-copy-id tool: ssh-copy-id user@remote-host
  
  – JucaPirama
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  11 hours ago
  

  
  
  
  

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 yesterday

HBruijnHBruijn

55.5k1090149

share|improve this answer

answered yesterday

HBruijnHBruijn

55.5k1090149

answered yesterday

HBruijnHBruijn

55.5k1090149

answered yesterday

HBruijnHBruijn

55.5k1090149