SSH, Actually 100% signal, 0% noise.

Permission Denied

troubleshooting
depth 2/3 − deeper + surface

SSH is opinionated about file permissions. If permissions are wrong, SSH silently refuses to use the key—no error message in normal mode, just "Permission denied." This is the single most common cause of "my key doesn't work" problems.

Why SSH cares: if a private key file is readable by other users, it might already be compromised. SSH would rather fail than use a key it can't trust. The same applies to authorized_keys on the server—if the file or its parent directories are writable by others, SSH ignores it entirely.

Fix all permissions at once, locally:

chmod 700 ~/.ssh
chmod 600 ~/.ssh/*
chmod 644 ~/.ssh/*.pub
chmod 644 ~/.ssh/known_hosts

And on the server:

chmod 755 ~/
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

The home directory matters. Even if ~/.ssh and authorized_keys are correct, the server rejects the key if your home directory is group- or world-writable. Server-side sshd requirement, and it trips people up constantly.