Lambda GPU cloud: SSH connection refused right after launch is normal

TL;DR

The default login user is ubuntu: ssh ubuntu@[instance IP]. After launch, wait 3-15 minutes for the instance to initialize before SSHing.

Fix

1. The default login user is ubuntu: ssh ubuntu@[instance IP]. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Lambda GPU cloud feature.
• The symptom matches: SSH connection refused right after launch is normal.

When NOT to use

• Unrelated Lambda GPU cloud issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Lambda GPU cloud. Source: https://github.com/majiayu000/hermes-agent/blob/HEAD/optional-skills/mlops/lambda-labs/SKILL.md.

Variant phrasings

SSH connection refused right after launch is normal

Why it happens

A fresh Lambda (lambda.ai) instance refuses SSH for the first minutes. Do not recreate it.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/majiayu000/hermes-agent/blob/HEAD/optional-skills/mlops/lambda-labs/SKILL.md

Source: A fresh Lambda (lambda.ai) instance refuses SSH for the first minutes. Do not recreate it.

Verified resolution: [lambda-labs skill]: after launch, wait 3-15 minutes for the instance to initialize before SSHing. The default login user is ubuntu: ssh ubuntu@[instance IP]. If it still refuses after 15 minutes, check the instance status in the console; recreating the instance just restarts the clock. Verify the stack after first login with nvidia-smi and a torch CUDA check.

Source URL: https://github.com/majiayu000/hermes-agent/blob/HEAD/optional-skills/mlops/lambda-labs/SKILL.md