Skip to main content

Connection Tester

Test SSH connectivity and verify credentials before adding a new host to Xermius. Save time by catching connection issues early.

What is Connection Tester?​

Simple Explanation: Connection Tester lets you verify that SSH credentials work before you create a host. Think of it as a "dry run" that checks everything is correct.

Benefits:

Without Connection Tester:
1. Create new host
2. Fill in all details
3. Try to connect
4. Connection fails!
5. Delete host
6. Try again...
Frustrating and time-consuming

With Connection Tester:
1. Test credentials first
2. If works → Create host confidently
3. If fails → Fix before creating
Quick and efficient

When to Use​

Before Adding New Host​

Perfect for:

  • ✅ Testing new server access
  • ✅ Verifying credentials are correct
  • ✅ Checking firewall allows SSH
  • ✅ Confirming port is correct
  • ✅ Testing network connectivity

Troubleshooting Existing Hosts​

Use to verify:

  • Password changed?
  • Firewall blocking?
  • Server accessible?
  • Port changed?
  • Network issues?

Team Setup Verification​

Confirm:

Admin: "I've set up access for you"
You: Test credentials first
Result: Works? → Create host
        Fails? → Ask admin to check

How to Use​

Access Connection Tester​

Location 1: Dashboard

1. Go to Hosts dashboard
2. Find "Test SSH Connection" card
3. Fill in credentials
4. Click "Test Connection"

Location 2: Before Creating Host

1. Click "New Host"
2. Fill in connection details
3. Click "Test Connection" button
4. Verify before saving

Testing a Connection​

Step 1: Fill in Details

┌────────────────────────────────────────┐
│ Test SSH Connection                    │
├────────────────────────────────────────┤
│ Test your credentials before adding    │
│                                        │
│ Host/IP Address: *                     │
│ [192.168.1.100            ]            │
│                                        │
│ Port:                                  │
│ [22                       ]            │
│                                        │
│ Username: *                            │
│ [root                     ]            │
│                                        │
│ Password: *                            │
│ [••••••••••]              [👁]         │
│                                        │
│      [Test Connection]                 │
└────────────────────────────────────────┘

Required fields:

  • Host/IP Address
  • Username
  • Password

Optional:

  • Port (defaults to 22)

Step 2: Click Test Connection

Status: Testing Connection...
[Spinner animation]

Connecting to 192.168.1.100:22...
Authenticating as root...

Step 3: View Result

Success:

┌────────────────────────────────────────┐
│ ✓ SSH connection successful!           │
│                                        │
│ You can now add this host.             │
│                                        │
│ Connection verified:                   │
│ • Host: 192.168.1.100                  │
│ • Port: 22                             │
│ • User: root                           │
│ • Auth: Password                       │
└────────────────────────────────────────┘

Failure:

┌────────────────────────────────────────┐
│ ✗ Connection failed                    │
│                                        │
│ Error: Authentication failed           │
│                                        │
│ Possible causes:                       │
│ • Wrong password                       │
│ • User doesn't exist                   │
│ • SSH not enabled                      │
└────────────────────────────────────────┘

Common Test Results​

Success Messages​

"SSH connection successful!"

✓ Everything works
✓ Credentials correct
✓ Server accessible
✓ SSH running

Action: Create host with these settings

Error Messages​

"Authentication failed"​

Causes:

  • Wrong password
  • Wrong username
  • SSH key expected (not password)
  • Account disabled

Solutions:

1. Verify password is correct
2. Check username (case-sensitive)
3. Try different user (ubuntu, admin, etc.)
4. Ask admin to verify account

"Connection timeout"​

Causes:

  • Wrong IP address
  • Server offline
  • Firewall blocking
  • Network unreachable

Solutions:

1. Ping server:
   ping 192.168.1.100

2. Check server is on

3. Verify IP address

4. Check firewall rules

"Connection refused"​

Causes:

  • SSH service not running
  • Wrong port
  • Firewall blocking port

Solutions:

1. On server, check SSH:
   systemctl status ssh
   systemctl status sshd

2. Try different ports:
   22 (default)
   2222 (alternate)
   Custom port

3. Check firewall:
   sudo ufw status
   sudo ufw allow 22

"Host not found"​

Causes:

  • Wrong hostname
  • DNS not working
  • Typo in address

Solutions:

1. Check hostname spelling

2. Try IP address instead

3. Test DNS:
   nslookup hostname

"Permission denied (publickey)"​

Causes:

  • Server requires SSH key
  • Password auth disabled

Solutions:

Server expects SSH key, not password

Use SSH key authentication instead:
1. Generate SSH key
2. Add key to server
3. Use key-based host in Xermius

Testing Different Scenarios​

Test with Different Ports​

Common SSH ports:

Standard: 22
Alternate: 2222
Custom: 2200, 2201, etc.

Test each:
Port: [22  ] → Test
Port: [2222] → Test
Port: [2200] → Test

Test Different Users​

Common usernames:

Linux:
- root
- ubuntu  
- admin
- your-name

Windows Server:
- Administrator
- admin

Try each until works

Test with Copy-Paste​

Avoid typos:

1. Copy password from password manager
2. Paste into password field
3. Copy hostname from documentation
4. Paste into host field

Eliminates typing errors

Best Practices​

1. Always Test Before Creating​

Don't:
✗ Create host
✗ Try to connect
✗ Fails
✗ Delete and retry

Do:
✓ Test connection first
✓ Works? Create host
✓ Fails? Fix then test again

2. Test After Server Changes​

When to retest:

  • Password changed
  • SSH reconfigured
  • Firewall updated
  • Server migrated
  • Port changed

Quick retest:

Use same test form
Update what changed
Verify still works

3. Document Working Settings​

After successful test:

Host: 192.168.1.100
Port: 22
User: root
Auth: Password ✓
Tested: Jan 17, 2024
Notes: Works from office network

4. Test from Same Network​

Important:

If server has firewall:
- May only allow specific IPs
- Test from actual location you'll use
- Office vs Home may differ

5. Use for Troubleshooting​

Host suddenly not connecting?

1. Use Connection Tester
2. Same credentials as saved host
3. Does test work?
   - Yes: Host config issue
   - No: Server/network issue

Troubleshooting Tips​

Test Won't Start​

Issue: Button disabled

Check:

□ Host field filled?
□ Username filled?
□ Password filled?
□ All 3 required!

Test Takes Forever​

Issue: Timeout after 30+ seconds

Likely causes:

- Server offline
- Network unreachable
- Firewall blocking
- Wrong IP

Cancel and check basics:
- Ping server
- Check network
- Verify IP

Test Says Success But Host Fails​

Issue: Test works, but host doesn't connect

Possible reasons:

1. Test disconnects after 2 seconds
   Host may have connection limits
   
2. Different auth method
   Test uses password
   Host configured for SSH key
   
3. Additional settings needed
   Host needs specific options
   
Solution: Check host configuration

Different Results Each Time​

Issue: Sometimes works, sometimes fails

Causes:

- Intermittent network
- Connection limits on server
- Load balancer rotating servers
- Firewall rate limiting

Solution:
- Test multiple times
- Check server logs
- Verify stable network

Use Cases​

Use Case 1: New Server Setup​

Scenario: Admin just set up server

1. Admin: "Server ready at 192.168.1.100"

2. Before creating host:
   Test Connection:
   Host: 192.168.1.100
   Port: 22
   User: deploy
   Pass: [from admin]

3. Test result: ✓ Success

4. Create host with confidence

5. No wasted time!

Use Case 2: Password Changed​

Scenario: Server password was rotated

1. Existing host can't connect

2. Use Connection Tester:
   Host: production.example.com
   User: admin
   Pass: [NEW password]

3. Test: ✓ Success

4. Update saved host password

5. Host works again!

Use Case 3: Multiple Servers​

Scenario: Setting up 10 servers

Don't: Create 10 hosts, test each

Do:
1. Test all 10 credentials first
2. Note which work
3. Create hosts for working ones
4. Fix others before creating
5. Much faster!

Use Case 4: Customer Access​

Scenario: Customer gave you credentials

Customer credentials sometimes wrong

1. Test first:
   Host: [customer server]
   User: [customer gave]
   Pass: [customer gave]

2. Result:
   ✗ Auth failed
   
3. Contact customer:
   "Credentials don't work, please verify"

4. Customer: "Oh sorry, wrong password!"

5. Test again with correct ones

6. ✓ Success → Create host

Security Notes​

Credentials Not Saved​

Connection Tester does NOT save:

✓ Credentials only in memory
✓ Cleared after test
✓ Not stored in database
✓ Not synced to cloud
✓ Only you see them

Safe to test:

  • Temporary passwords
  • Customer credentials
  • Shared accounts
  • Test accounts

Test Connection Auto-Closes​

After successful test:

1. Connection established
2. "Success" message shown
3. After 2 seconds → Auto-disconnect
4. Resources cleaned up
5. No lingering connections

Use Secure Network​

Best practice:

Test from:
✓ Trusted networks
✓ VPN if needed
✓ Same network as you'll use

Avoid:
✗ Public WiFi (unless VPN)
✗ Untrusted networks

Quick Reference​

Test Checklist​

Before testing:
□ Have correct IP/hostname
□ Know correct port
□ Have valid username
□ Have current password
□ On proper network

During test:
□ Fill all required fields
□ Double-check for typos
□ Click Test Connection
□ Wait for result

After success:
□ Note working configuration
□ Create host with same settings
□ Document for future reference

After failure:
□ Read error message
□ Check common causes
□ Fix issue
□ Test again

Common Port Numbers​

SSH:     22, 2222
HTTP:    80
HTTPS:   443
MySQL:   3306
PostgreSQL: 5432
MongoDB: 27017
Redis:   6379

Next Steps​