Selfhosted

39903 readers

463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

SSH Key Strangeness (lemmygrad.ml)

submitted 1 year ago* (last edited 1 year ago) by BRINGit34@lemmygrad.ml to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

Are there any reasons to get a pubkey denied after you run ssh-copy-id onto your server? I've already restarted the sshd service but I still get pubkey denied after I copied my ssh I.D. to my server. I am thinking about just removing all the keys I have on the server and re-adding them but I was hoping someone else may have an idea before I do that. Thanks!

EDIT: OKAY. I fixed it. I appreciate all the help I received. I still really could not figure out what the actual issue is. But I did have some extra ssh keys that I wasn't using from old machines and after I deleted those and readded my key everything seems to work

top 8 comments

sorted by: hot top controversial new old

[–] brain_in_a_jar@lemmy.world 7 points 1 year ago

Check perms on the ~/.ssh/authorized_keys file on the server side (should be 0600) and the ~/.ssh dir itself?

[–] leopardboy@netmonkey.tech 5 points 1 year ago (1 children)

Have you confirmed that the public keys exist on the remote server in your .ssh directory? Are the permissions correct?

[–] BRINGit34@lemmygrad.ml 1 points 1 year ago (1 children)

I'll have to check when I get off work. I never have any errors when copying my id so I am not sure why they wouldn't be there but I will check

[–] leopardboy@netmonkey.tech 2 points 1 year ago

Same. I've never had it screw up before, but the only thing I can imagine is that something's not right with the keys.

As an aside, I did recently create a new server, and somehow managed to completely ignore the errors in ssh-copy-id. Turns out I forgot to use -m (to create my home directory) in useradd when I went to create my personal account. Oops!

[–] uin@lemmy.world 4 points 1 year ago

Also: Make sure that the user you ran “ssh-copy-id” against on the remote machine is also the user you’re trying to log in with.

[–] r0ckr@lemmy.world 2 points 1 year ago

Try running this command on your target system:

cat $HOME/.ssh/authorized_keys

Does the private key part of your key pair show up in the list?

[–] TCB13@lemmy.world 1 points 1 year ago

How many private keys do you have in your client machine? Sometimes people generate a new key par but there's a previous one on the system that gets served before the right one. Go into your .ssh directory in the client and check if there's anything else there.

[–] mirisbowring@lemmy.primboard.de 1 points 1 year ago

did you verify to use the correct corresponding private key?

You can specify the keyfile with the -i option if i remember correctly