SSH to droplet with non root user
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
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.
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
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
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.
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
ssh
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
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
asked Mar 20 at 13:08
Jonas GrønbekJonas Grønbek
1084
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.
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.
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 |
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
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
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 Answer
1
active
oldest
votes
"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.
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
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
2 days ago
@JucaPiramassh-copy-id user@remote-hostleaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
– HBruijn
2 days 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.
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
"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.
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
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
2 days ago
@JucaPiramassh-copy-id user@remote-hostleaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
– HBruijn
2 days 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.
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
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
2 days ago
@JucaPiramassh-copy-id user@remote-hostleaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
– HBruijn
2 days 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.
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
"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.
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
answered Mar 20 at 13:20
HBruijnHBruijn
55.6k1090149
55.6k1090149
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
2 days ago
@JucaPiramassh-copy-id user@remote-hostleaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
– HBruijn
2 days ago
add a comment |
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
2 days ago
@JucaPiramassh-copy-id user@remote-hostleaves you in a bit of a catch-22 when your SSHD configuration does not allow password authentication (which is quite strongly recommended).
– HBruijn
2 days ago
1
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
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
2 days ago
It would be simpler using the ssh-copy-id tool:
ssh-copy-id user@remote-host– JucaPirama
2 days 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
2 days 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
2 days ago
add a comment |
Jonas Grønbek is a new contributor. Be nice, and check out our Code of Conduct.
Jonas Grønbek is a new contributor. Be nice, and check out our Code of Conduct.
Jonas Grønbek is a new contributor. Be nice, and check out our Code of Conduct.
Jonas Grønbek is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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