Skip to content

v0.4.0 — robust machine start recovery

Choose a tag to compare

@Okymi-X Okymi-X released this 21 Jun 12:47

Fixes

htb machine start is now resilient to two failure modes seen on a stuck box.

1. Recover from 403: You already have an active instance

Previously this lock had no recovery — the start failed and you had to manually stop then start. Now start inspects what is actually active and reacts idempotently:

  • Same machine, already running → reported as-is (no churn).
  • Same machine, assigned but not spawned → reclaimed automatically (terminate + restart).
  • A different machine is active → never touched; clear, actionable error naming it.

2. --wait now honors --retry-for and fails fast on collapse

  • The IP poll previously ignored --retry-for (hidden 300s cap). --retry-for now budgets the whole --wait flow.
  • It kept printing waiting for machine IP... even after the instance vanished. It now fails fast with a real diagnosis when the spawn collapses on HTB's side (active machine drops out or is replaced) and reminds you to confirm the matching VPN lab server.

Full changelog: v0.3.0...v0.4.0