Debian 7 VPS SSH无密码提示且认证失败问题求助

Hey there, sorry to hear you're hitting this frustrating SSH issue with your long-running Debian 7 VPS. Let's break down actionable troubleshooting steps to get you back in:

1. Check SSH Server Logs First #

The fastest way to pinpoint the root cause is to look at the auth logs on your VPS. If you can access the server via a web-based control panel (like SolusVM) or a direct console (KVM/IPMI), run this command to pull recent SSH-related logs:

tail -n 50 /var/log/auth.log

Look for lines containing sshd—they’ll tell you exactly why authentication failed: it could be a PAM configuration error, a locked user account, failed key attempts triggering MaxAuthTries, or disk space issues preventing log writes.

2. Verify SSHD Configuration #

Head to /etc/ssh/sshd_config and double-check these critical settings (use nano /etc/ssh/sshd_config to edit if needed):

• Ensure PasswordAuthentication yes is uncommented and set to yes (if you rely on password login)
• Confirm UsePAM yes is enabled—PAM handles password prompts, so disabling this will skip the password prompt entirely
• Check MaxAuthTries isn’t set to an extremely low value (like 1) which would trigger a failure before you can enter a password
• If logging in as root, make sure PermitRootLogin is set to yes (or prohibit-password only if you use key auth)

After making changes, restart the SSH service with:

service ssh restart

3. Inspect PAM Configuration for SSH #

Debian 7 uses PAM to manage authentication, so a broken PAM config for SSH can cause silent failures. Check /etc/pam.d/sshd and ensure it includes this line (which loads the common password auth rules):

@include common-auth

If this line is missing or commented out, SSH won’t prompt for a password. Restore it and restart the SSH service.

4. Check System Resources #

A full disk or exhausted memory can break SSH authentication:

• Run df -h to check if any filesystem (especially / or /var) is 100% full. If so, clear out old logs or unused files to free space.
• Use free -m to verify you have enough available memory—low memory can cause sshd to behave unpredictably.

5. Debug from the Client Side #

On your local machine, run SSH in verbose mode to see the step-by-step connection process:

ssh -v your-username@your-vps-ip

This will show you exactly where the process hangs—whether the server isn’t sending a password prompt, or if an authentication method is being rejected. Look for lines like debug1: Authentications that can continue: to see what methods the server accepts.

6. Rule Out Firewall/Ban Issues #

• Check if your IP was accidentally blocked by fail2ban (common if you had multiple failed attempts):

  fail2ban-client status sshd
  

  If your IP is listed, unban it with fail2ban-client set sshd unbanip your-local-ip.
• Verify iptables rules aren’t blocking SSH connections:

  iptables -L -n
  

  Ensure there’s a rule allowing incoming traffic on port 22.

7. Check for Recent Changes #

Think back—did you recently update the SSH package, modify user accounts, or change any system configs? Debian 7 is end-of-life, so updates might overwrite default configs. If you modified the user’s password recently, confirm it’s correct via the VPS console.

Hopefully one of these steps gets you back into your server!

内容的提问来源于stack exchange，提问作者angico