Tools: ๐Ÿš€ How I Configured SSH Access from My Local Linux Mint to a VPS - Expert Insights

Tools: ๐Ÿš€ How I Configured SSH Access from My Local Linux Mint to a VPS - Expert Insights

๐Ÿš€ How I Configured SSH Access from My Local Linux Mint to a VPS

๐Ÿง  Architecture Overview (Diagram)

๐Ÿ” Step 1: Generate SSH Key (Custom Name)

๐Ÿ“ค Step 2: Copy Public Key to VPS

๐Ÿงช Step 3: Test SSH Connection

โš™๏ธ Step 4: SSH Config for Clean Access

โšก Step 5: Connect with Simple Command

๐Ÿ”’ Security & Best Practices

๐Ÿš€ Final Thoughts A clean DevOps-style SSH setup for secure and fast server access. Instead of default keys like id_rsa, I created a dedicated key for this server: This installs the public key into: Once successful, we move to automation. Now access the server with: No IP, no port, no key flags. If you manage multiple servers, this setup is a must-have for scaling your workflow like a professional DevOps engineer. Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse

Command

Copy

$ flowchart LR A[Local Linux Mint Machine] --> B[SSH Key Pair] B --> C[Private Key: moti-dig-1] B --> D[Public Key: moti-dig-1.pub] D --> E[VPS Server] E --> F[~/.ssh/authorized_keys] A -->|ssh moti-dig-1| E flowchart LR A[Local Linux Mint Machine] --> B[SSH Key Pair] B --> C[Private Key: moti-dig-1] B --> D[Public Key: moti-dig-1.pub] D --> E[VPS Server] E --> F[~/.ssh/authorized_keys] A -->|ssh moti-dig-1| E flowchart LR A[Local Linux Mint Machine] --> B[SSH Key Pair] B --> C[Private Key: moti-dig-1] B --> D[Public Key: moti-dig-1.pub] D --> E[VPS Server] E --> F[~/.ssh/authorized_keys] A -->|ssh moti-dig-1| E ssh-keygen -t ed25519 -C "moti-dig-1" -f ~/.ssh/moti-dig-1 ssh-keygen -t ed25519 -C "moti-dig-1" -f ~/.ssh/moti-dig-1 ssh-keygen -t ed25519 -C "moti-dig-1" -f ~/.ssh/moti-dig-1 ssh-copy-id -i ~/.ssh/moti-dig-1.pub -p 44 [email protected] ssh-copy-id -i ~/.ssh/moti-dig-1.pub -p 44 [email protected] ssh-copy-id -i ~/.ssh/moti-dig-1.pub -p 44 [email protected] ~/.ssh/authorized_keys ~/.ssh/authorized_keys ~/.ssh/authorized_keys ssh -i ~/.ssh/moti-dig-1 -p 44 [email protected] ssh -i ~/.ssh/moti-dig-1 -p 44 [email protected] ssh -i ~/.ssh/moti-dig-1 -p 44 [email protected] nano ~/.ssh/config nano ~/.ssh/config nano ~/.ssh/config Host moti-dig-1 HostName 165.22.104.176 User root Port 44 IdentityFile ~/.ssh/moti-dig-1 StrictHostKeyChecking accept-new Host moti-dig-1 HostName 165.22.104.176 User root Port 44 IdentityFile ~/.ssh/moti-dig-1 StrictHostKeyChecking accept-new Host moti-dig-1 HostName 165.22.104.176 User root Port 44 IdentityFile ~/.ssh/moti-dig-1 StrictHostKeyChecking accept-new ssh moti-dig-1 ssh moti-dig-1 ssh moti-dig-1 chmod 600 ~/.ssh/moti-dig-1 chmod 600 ~/.ssh/config chmod 600 ~/.ssh/moti-dig-1 chmod 600 ~/.ssh/config chmod 600 ~/.ssh/moti-dig-1 chmod 600 ~/.ssh/config - ~/.ssh/moti-dig-1 โ†’ Private key - ~/.ssh/moti-dig-1.pub โ†’ Public key - Use ed25519 keys (modern & secure) - Keep one key per server/project - Use SSH config for clean workflow - Set proper permissions: - Security ๐Ÿ” - Productivity โšก - Maintainability ๐Ÿงน - DevOps readiness โ˜๏ธ