Files
proxmox/docs/09-troubleshooting/ssh-r630-04-options.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

4.0 KiB

SSH Connection Options for R630-04

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

IP: 192.168.11.14
User: root
Issue: Permission denied with password authentication.


Possible Causes

  1. Password incorrect - Double-check the password
  2. Password authentication disabled - Server may require key-based auth
  3. Account locked - Too many failed attempts
  4. SSH configuration - Server may have restrictive settings
  5. Wrong user - May need different username

Troubleshooting Steps

1. Check SSH Authentication Methods

From another host that can connect to R630-04, check:

ssh -v root@192.168.11.14 2>&1 | grep -i "auth"

Look for:

  • publickey - Key-based authentication enabled
  • password - Password authentication enabled
  • keyboard-interactive - Interactive password prompt

2. Try Different Authentication Methods

Option A: Use SSH Key (if available)

# Check for existing SSH keys
ls -la ~/.ssh/id_*

# Copy public key to R630-04 (if you have access from another host)
ssh-copy-id root@192.168.11.14

Option B: Check if password has special characters

The password L@kers2010 contains @ which should work, but try:

  • Typing it carefully
  • Using copy-paste
  • Checking for hidden characters

3. Connect from R630-03 (which works)

Since R630-03 works, you can:

# SSH to R630-03 first
ssh root@192.168.11.13
# Password: L@kers2010

# Then from R630-03, SSH to R630-04
ssh root@192.168.11.14

4. Check SSH Configuration on R630-04

If you have console access or another way to access R630-04:

# Check SSH configuration
cat /etc/ssh/sshd_config | grep -E "PasswordAuthentication|PubkeyAuthentication|PermitRootLogin"

# Should show:
# PasswordAuthentication yes (or the line commented out)
# PubkeyAuthentication yes
# PermitRootLogin yes (or prohibit-password)

5. Reset Root Password (if you have console access)

If you have physical/console access:

# Boot into single user mode or recovery
# Then reset password:
passwd root

6. Check Account Status

# Check if root account is locked
passwd -S root

# Check failed login attempts
lastb | grep root | tail -20

Alternative Access Methods

1. Use Proxmox Console

If R630-04 is managed by another Proxmox host:

# From Proxmox host managing R630-04
pct enter <container-id>  # if it's a container
# or
qm monitor <vm-id>  # if it's a VM

2. Use iDRAC/iLO (Dell R630)

If it's a physical Dell R630 server:

  • Access iDRAC interface (usually https://)
  • Use remote console
  • Reset password from console

3. Network Boot/KVM Access

If you have KVM over IP or network boot access, you can:

  • Access console directly
  • Reset password
  • Check SSH configuration

Quick Verification

Try these commands from R630-03 (which works):

# From R630-03
ssh root@192.168.11.13
# After logging in, try:
ssh -v root@192.168.11.14 2>&1 | grep -E "auth|password|key"

  1. Try connecting from R630-03 - Sometimes network path matters
  2. Verify password - Try typing it again carefully
  3. Check if password was changed - May have been changed since last login
  4. Use console access - If available (iDRAC, KVM, etc.)
  5. Check SSH logs on R630-04 - /var/log/auth.log or journalctl -u ssh

If Password Authentication is Disabled

If the server only accepts SSH keys:

  1. Generate SSH key pair (on your local machine):

    ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519_r630-04
    
  2. Copy public key (if you have another way to access):

    # Method 1: If you have access from R630-03
    ssh root@192.168.11.13
    ssh-copy-id -i ~/.ssh/id_ed25519_r630-04.pub root@192.168.11.14
    
    # Method 2: Manual copy (if you have console access)
    # Copy the public key content to:
    # /root/.ssh/authorized_keys on R630-04
    
  3. Connect with key:

    ssh -i ~/.ssh/id_ed25519_r630-04 root@192.168.11.14